{"success":true,"homev2":true,"incidentsFeedError":false,"ongoing":[{"title":"Zscaler Client Connector (ZCC) Device Registration Failures","link":"https://trust.zscaler.com/posts/30636","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 23:29:35 UTC</span></p><p>Zscaler has identified the underlying cause and is working on both an immediate mitigation and a permanent fix. As a temporary relief measure, Zscaler is implementing a change to reduce the amount of group membership information included during device registration for affected users. A permanent product fix is also in development. Further updates will be shared as more information becomes available.</p></div>","pubDate":"Fri, 10 Jul 2026 21:55:13 GMT","guid":"30636 at https://trust.zscaler.com","id":"30636","clouds":["zscalertwo.net","zscalerthree.net"],"updates":[{"time":"Fri, 10 Jul 2026 23:29:35 UTC","update":"Zscaler has identified the underlying cause and is working on both an immediate mitigation and a permanent fix. As a temporary relief measure, Zscaler is implementing a change to reduce the amount of group membership information included during device registration for affected users. A permanent product fix is also in development. Further updates will be shared as more information becomes available.","status":"In-Progress"}],"latest_update":[{"time":"Fri, 10 Jul 2026 23:29:35 UTC","update":"Zscaler has identified the underlying cause and is working on both an immediate mitigation and a permanent fix. As a temporary relief measure, Zscaler is implementing a change to reduce the amount of group membership information included during device registration for affected users. A permanent product fix is also in development. Further updates will be shared as more information becomes available.","status":"In-Progress"}],"root_cause":"","startTime":"Fri, 10 Jul 2026 21:00:01 GMT","endTime":null,"eventType":"Service Degradation","customerImpact":"Affected users may see a “Device Registration Failed” message with error code 3053 and may be unable to complete device registration or access services.\r\n\r\nAt this time, this issue does not affect all users or all customers. Based on current findings, the impact appears to be limited to users with a high number of group memberships.","availableWorkaround":"<p>As a temporary mitigation, customers may review whether affected users have a high volume of group memberships, as this may contribute to the issue.&nbsp;</p>","nextUpdate":"13 Jul 2026 22:00 UTC","summary":"","category":{"name":"Recent incident","domain":"https://trust.zscaler.com"},"current_status":"In Progress","originalData":{"id":"30636","title":"Zscaler Client Connector (ZCC) Device Registration Failures","clouds":"[Circular Reference]","link":"https://trust.zscaler.com/posts/30636","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 23:29:35 UTC</span></p><p>Zscaler has identified the underlying cause and is working on both an immediate mitigation and a permanent fix. As a temporary relief measure, Zscaler is implementing a change to reduce the amount of group membership information included during device registration for affected users. A permanent product fix is also in development. Further updates will be shared as more information becomes available.</p></div>","updates":[{"time":"Fri, 10 Jul 2026 23:29:35 UTC","update":"Zscaler has identified the underlying cause and is working on both an immediate mitigation and a permanent fix. As a temporary relief measure, Zscaler is implementing a change to reduce the amount of group membership information included during device registration for affected users. A permanent product fix is also in development. Further updates will be shared as more information becomes available.","status":"In-Progress"}],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Fri, 10 Jul 2026 21:55:13 GMT","resolved_date":null,"startTime":"Fri, 10 Jul 2026 21:00:01 GMT","endTime":"","eventType":"Service Degradation","customerImpact":"Affected users may see a “Device Registration Failed” message with error code 3053 and may be unable to complete device registration or access services.\r\n\r\nAt this time, this issue does not affect all users or all customers. Based on current findings, the impact appears to be limited to users with a high number of group memberships.","availableWorkaround":"<p>As a temporary mitigation, customers may review whether affected users have a high volume of group memberships, as this may contribute to the issue.&nbsp;</p>","nextUpdate":"13 Jul 2026 22:00 UTC","summary":"","category":"[Circular Reference]","current_status":"In Progress","how_found":"Customer Reported"},"feedUrl":"https://trust.zscaler.com/rss-feed/incidents?_format=json","trustEnvironment":"Commercial","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-07-10T22:02:00.641Z","lastUpdated":"2026-07-10T23:52:00.524Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-07-10T21:00:01.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/mlzxjtx6z07y","title":"Last Mile node LM - Indore, IN - Airtel offline","description":"<p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>06:08</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Indore, IN - Airtel will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Fri, 10 Jul 2026 06:08:30 +0000","link":"https://lmstatus.catchpoint.com/incidents/mlzxjtx6z07y","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-10T06:08:00.000Z","resolved_at":null,"startTime":"2026-07-10T06:08:00.000Z","endTime":null,"updatedAt":"2026-07-10T06:08:00.000Z","location":"Indore","country":"IN","provider":"Airtel offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-10T06:08:00.000Z","_parsedEndTime":null},{"id":"df9xgd1h232c","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Tel Aviv</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-07-09T04:27:49.860Z","link":"https://stspg.io/kn60x45rvb2r","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-09T04:27:49.860Z","resolved_at":null,"startTime":"2026-07-09T04:27:49.860Z","endTime":null,"updatedAt":"2026-07-09T04:27:49.866Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"gytlmjyct80z","status":"investigating","body":"<p><strong>Update:</strong> Changes to Locations</p><p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Doha, Riyadh, Tel Aviv</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"df9xgd1h232c","created_at":"2026-07-09T04:27:49.860Z","updated_at":"2026-07-09T04:27:49.860Z","display_at":"2026-07-09T04:27:49.860Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"99b5wxtpp5hj","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Tel Aviv</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"df9xgd1h232c","created_at":"2026-06-17T23:09:02.139Z","updated_at":"2026-06-17T23:09:02.139Z","display_at":"2026-06-17T23:09:02.139Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"df9xgd1h232c","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-09T04:27:49.860Z","_parsedEndTime":null},{"id":"sxqfl8d1wx7p","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Sydney</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-07-09T04:22:20.256Z","link":"https://stspg.io/c9rfpg8btwr9","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-09T04:22:20.256Z","resolved_at":null,"startTime":"2026-07-09T04:22:20.256Z","endTime":null,"updatedAt":"2026-07-09T04:22:20.261Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"9jj6y963d7n3","status":"investigating","body":"<p><strong>Update:</strong> Changes to Locations</p><p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Hong Kong, Jakarta, Mumbai, Osaka, Seoul, Singapore, Sydney, Taipei, Tokyo</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"sxqfl8d1wx7p","created_at":"2026-07-09T04:22:20.256Z","updated_at":"2026-07-09T04:22:20.256Z","display_at":"2026-07-09T04:22:20.256Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"x4hl83zt5jvd","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Sydney</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"sxqfl8d1wx7p","created_at":"2026-06-17T22:53:18.986Z","updated_at":"2026-06-17T22:53:18.986Z","display_at":"2026-06-17T22:53:18.986Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"sxqfl8d1wx7p","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-09T04:22:20.256Z","_parsedEndTime":null},{"id":"707f1mcwyk1d","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Eemshaven</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-07-09T04:13:48.039Z","link":"https://stspg.io/z4p9sdn8c597","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-09T04:13:48.039Z","resolved_at":null,"startTime":"2026-07-09T04:13:48.039Z","endTime":null,"updatedAt":"2026-07-09T04:13:48.044Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"5d9w68bm9rv8","status":"investigating","body":"<p><strong>Update:</strong> Changes to Locations</p><p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Berlin, Eemshaven, Frankfurt, London, Madrid, Milan, Paris, Warsaw, Zurich</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"707f1mcwyk1d","created_at":"2026-07-09T04:13:48.039Z","updated_at":"2026-07-09T04:13:48.039Z","display_at":"2026-07-09T04:13:48.039Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"c74r5w9brdxf","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Eemshaven</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"707f1mcwyk1d","created_at":"2026-06-17T22:53:14.034Z","updated_at":"2026-06-17T22:53:14.034Z","display_at":"2026-06-17T22:53:14.034Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"707f1mcwyk1d","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-09T04:13:48.039Z","_parsedEndTime":null},{"id":"gznlrf0m50sc","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Council Bluffs</p><p><strong>Impact:</strong></p><p>Email notifications are temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-07-09T04:03:48.365Z","link":"https://stspg.io/d74370c4p2k8","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-09T04:03:48.365Z","resolved_at":null,"startTime":"2026-07-09T04:03:48.365Z","endTime":null,"updatedAt":"2026-07-09T04:03:48.370Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"xq4mf1bf7gtw","status":"investigating","body":"<p><strong>Update:</strong> Changes to Locations</p><p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Council Bluffs, Montreal</p><p><strong>Impact:</strong></p><p>Email notifications are temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"gznlrf0m50sc","created_at":"2026-07-09T04:03:48.365Z","updated_at":"2026-07-09T04:03:48.365Z","display_at":"2026-07-09T04:03:48.365Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"ptfv4pvd6f9w","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Council Bluffs</p><p><strong>Impact:</strong></p><p>Email notifications are temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"gznlrf0m50sc","created_at":"2026-06-17T22:49:21.477Z","updated_at":"2026-06-17T22:49:21.477Z","display_at":"2026-06-17T22:49:21.477Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"gznlrf0m50sc","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-09T04:03:48.365Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/dz929wm74wdw","title":"Wireless node Los Angeles - TMobile 5G offline","description":"<p> <small>Jul <var data-var='date'> 8</var>, <var data-var='time'>22:57</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Wireless node Los Angeles - TMobile 5G will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Wed, 08 Jul 2026 22:57:22 +0000","link":"https://lmstatus.catchpoint.com/incidents/dz929wm74wdw","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-08T22:57:00.000Z","resolved_at":null,"startTime":"2026-07-08T22:57:00.000Z","endTime":null,"updatedAt":"2026-07-08T22:57:00.000Z","location":null,"country":null,"provider":null,"nodeType":"wireless","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-08T22:57:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/6l0hfdhjg8z3","title":"Last Mile node LM - Woburn, US - Verizon offline","description":"<p> <small>Jul <var data-var='date'> 5</var>, <var data-var='time'>16:54</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Woburn, US - Verizon will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Sun, 05 Jul 2026 16:54:13 +0000","link":"https://lmstatus.catchpoint.com/incidents/6l0hfdhjg8z3","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-05T16:54:00.000Z","resolved_at":null,"startTime":"2026-07-05T16:54:00.000Z","endTime":null,"updatedAt":"2026-07-05T16:54:00.000Z","location":"Woburn","country":"US","provider":"Verizon offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-05T16:54:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/hk252yzgvb41","title":"Last Mile node LM - Amritsar, IN - Airtel offline","description":"<p> <small>Jul <var data-var='date'> 4</var>, <var data-var='time'>10:56</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Amritsar, IN - Airtel will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Sat, 04 Jul 2026 10:56:47 +0000","link":"https://lmstatus.catchpoint.com/incidents/hk252yzgvb41","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-04T10:56:00.000Z","resolved_at":null,"startTime":"2026-07-04T10:56:00.000Z","endTime":null,"updatedAt":"2026-07-04T10:56:00.000Z","location":"Amritsar","country":"IN","provider":"Airtel offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-04T10:56:00.000Z","_parsedEndTime":null},{"id":"tag:status.tines.com,2005:Incident/x6aSNr","published":"2026-07-02T23:39:53.000Z","updated":"2026-07-02T23:39:23Z","link":"https://status.tines.com/incidents/x6aSNr","title":"Potential impact to self hosted customers who adopted Helm charts prior to January 26, 2026.","content":{"_":"<small>2026-07-02 23:39:23 UTC</small><br /><strong>Problem detected [<em>Investigating</em>]</strong><br />Upgrading a self hosted instance with the current Helm charts customers are at risk of deleting the current namespace and potential data loss.\n\nSelf hosted customers who adopted Helm charts prior to January 26, 2026 are advised to not upgrade their self hosted instances via Helm charts until further advised.\n\nThe Engineering team are investigating this behaviour and we will notify affected customers when they can safely upgrade via Helm charts.\n\nThank you for your patience and we apologize for any inconvenience caused. \n\nPlease contact Tines support should you have any questions.","html":"true"},"description":"<small>2026-07-02 23:39:23 UTC</small><br /><strong>Problem detected [<em>Investigating</em>]</strong><br />Upgrading a self hosted instance with the current Helm charts customers are at risk of deleting the current namespace and potential data loss.\n\nSelf hosted customers who adopted Helm charts prior to January 26, 2026 are advised to not upgrade their self hosted instances via Helm charts until further advised.\n\nThe Engineering team are investigating this behaviour and we will notify affected customers when they can safely upgrade via Helm charts.\n\nThank you for your patience and we apologize for any inconvenience caused. \n\nPlease contact Tines support should you have any questions.","pubDate":"2026-07-02T23:39:23.000Z","guid":"tag:status.tines.com,2005:Incident/x6aSNr","feedType":"incidents","feedCategory":"status-page","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.tines.com/incidents.atom","firstSeen":"2026-07-02T23:41:00.527Z","lastUpdated":"2026-07-02T23:41:00.527Z","vendor":"Tines","vendorId":"tines","startTime":"2026-07-02T23:39:23.000Z","endTime":null,"created_at":"2026-07-02T23:39:23.000Z","resolved_at":null,"updatedAt":"2026-07-02T23:39:23Z","status":"investigating","impact":"none","incidentUpdates":[],"isResolved":false,"healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","_parsedIsResolved":false,"_parsedStartTime":"2026-07-02T23:39:23.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/t2lplmd0mdx3","title":"Last Mile node LM - Suwanee, US - AT&T offline","description":"<p> <small>Jul <var data-var='date'> 2</var>, <var data-var='time'>18:28</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Suwanee, US - AT&T will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Thu, 02 Jul 2026 18:28:43 +0000","link":"https://lmstatus.catchpoint.com/incidents/t2lplmd0mdx3","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-02T18:28:00.000Z","resolved_at":null,"startTime":"2026-07-02T18:28:00.000Z","endTime":null,"updatedAt":"2026-07-02T18:28:00.000Z","location":"Suwanee","country":"US","provider":"AT&T offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-02T18:28:00.000Z","_parsedEndTime":null},{"id":"betterstack-status-report-939239","guid":"betterstack-status-report-939239","title":"Elevated error rate – AWS CDN (Singapore)","description":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","pubDate":"2026-06-30T08:30:56.000Z","link":"https://status.huggingface.co/incident/939239","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-30T08:30:56.000Z","resolved_at":null,"started_at":"2026-06-30T08:30:56.000Z","startTime":"2026-06-30T08:30:56.000Z","endTime":null,"updatedAt":"2026-06-30T08:30:56.000Z","incidentUpdates":[{"body":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","created_at":"2026-06-30T08:30:56.000Z","status":"investigating"}],"affectedComponents":[{"name":"Elevated error rate – AWS CDN (Singapore)"}],"originalData":{"rssUpdates":[{"title":"Elevated error rate – AWS CDN (Singapore)","link":"https://status.huggingface.co/incident/939239","pubDate":"Tue, 30 Jun 2026 08:30:56 -0000","guid":"https://status.huggingface.co/incident/939239#f70161cc2145a0c230d3e7ca02109956a6d926b6cf56b448188b3c14a599fbfd","description":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-30T08:32:00.910Z","lastUpdated":"2026-06-30T08:32:00.910Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":"939239"},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-06-30T08:30:56.000Z","_parsedEndTime":null},{"id":"betterstack-status-report-939240","guid":"betterstack-status-report-939240","title":"Elevated error rate – AWS CDN (Singapore)","description":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","pubDate":"2026-06-30T07:58:00.000Z","link":"https://status.huggingface.co/incident/939240","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-30T07:58:00.000Z","resolved_at":null,"started_at":"2026-06-30T07:58:00.000Z","startTime":"2026-06-30T07:58:00.000Z","endTime":null,"updatedAt":"2026-06-30T07:58:00.000Z","incidentUpdates":[{"body":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","created_at":"2026-06-30T07:58:00.000Z","status":"investigating"}],"affectedComponents":[{"name":"Elevated error rate – AWS CDN (Singapore)"}],"originalData":{"rssUpdates":[{"title":"Elevated error rate – AWS CDN (Singapore)","link":"https://status.huggingface.co/incident/939240","pubDate":"Tue, 30 Jun 2026 07:58:00 -0000","guid":"https://status.huggingface.co/incident/939240#3c97443b5b5c62a6894d2a3ed7e14e1d53cba1565da2ab0cd604683de7b57b6a","description":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-30T08:37:01.236Z","lastUpdated":"2026-06-30T08:37:01.236Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":"939240"},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-06-30T07:58:00.000Z","_parsedEndTime":null},{"id":"fastly-incident-378629","title":"Mumbai (QAI) Rerouted Traffic","description":"<p><font color=\"#636363\"><span style=\"font-size: 14px; font-family: Helvetica\">Traffic in Mumbai (QAI) has been temporarily rerouted.<br><br>All other locations and services are unaffected.</span></font></p>","pubDate":"2026-06-30T07:16:00.000Z","link":"https://www.fastlystatus.com/incident/378629","status":"unknown","impact":"none","isResolved":false,"created_at":"2026-06-30T07:16:00.000Z","resolved_at":null,"started_at":"2026-06-30T07:16:00.000Z","startTime":"2026-06-30T07:16:00.000Z","endTime":null,"updatedAt":"2026-06-30T07:16:00.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"fastly-incident-378629","originalData":{"title":"Mumbai (QAI) Rerouted Traffic","description":"<p><font color=\"#636363\"><span style=\"font-size: 14px; font-family: Helvetica\">Traffic in Mumbai (QAI) has been temporarily rerouted.<br><br>All other locations and services are unaffected.</span></font></p>","link":"https://www.fastlystatus.com/incident/378629","guid":"/378629/816829","pubDate":"Tue, 30 Jun 2026 07:16:00 +0000","sc:customfields":"[]","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://www.fastlystatus.com/rss","firstSeen":"2026-06-30T08:46:00.754Z","lastUpdated":"2026-06-30T08:46:00.754Z","source":"rss-feed"},"source":"rss-feed","vendor":"Fastly","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"fastly","_parsedIsResolved":true,"_parsedStartTime":"2026-06-30T07:16:00.000Z","_parsedEndTime":null},{"title":"Intermittent DNS Resolution Failures for Wildcard Domains","link":"https://trust.zscaler.com/posts/30451","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Wed, 01 Jul 2026 22:55:15 UTC</span></p><p>Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 22:57:26 UTC</span></p><p>Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:18 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:00:34 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-5\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:02:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","pubDate":"Wed, 01 Jul 2026 17:42:58 GMT","guid":"30451 at https://trust.zscaler.com","id":"30451","clouds":["zscaler.net","zscalertwo.net","zscloud.net","zscalerthree.net"],"updates":[{"time":"Wed, 01 Jul 2026 22:55:15 UTC","update":"Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Thu, 02 Jul 2026 22:57:26 UTC","update":"Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:18 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:00:34 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:02:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":[{"time":"Fri, 10 Jul 2026 06:02:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"root_cause":"","startTime":"Tue, 30 Jun 2026 02:50:00 GMT","endTime":null,"eventType":"Service Degradation","customerImpact":"Customers may experience intermittent DNS resolution failures on both Private Service Edges and Public Service Edges when accessing wildcard domains that resolve to more than 256 IP addresses.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":{"name":"Recent incident","domain":"https://trust.zscaler.com"},"current_status":"In Progress","originalData":{"id":"30451","title":"Intermittent DNS Resolution Failures for Wildcard Domains","clouds":"[Circular Reference]","link":"https://trust.zscaler.com/posts/30451","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Wed, 01 Jul 2026 22:55:15 UTC</span></p><p>Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 22:57:26 UTC</span></p><p>Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:18 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:00:34 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-5\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:02:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","updates":[{"time":"Wed, 01 Jul 2026 22:55:15 UTC","update":"Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Thu, 02 Jul 2026 22:57:26 UTC","update":"Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:18 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:00:34 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:02:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Wed, 01 Jul 2026 17:42:58 GMT","resolved_date":null,"startTime":"Tue, 30 Jun 2026 02:50:00 GMT","endTime":"","eventType":"Service Degradation","customerImpact":"Customers may experience intermittent DNS resolution failures on both Private Service Edges and Public Service Edges when accessing wildcard domains that resolve to more than 256 IP addresses.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":"[Circular Reference]","current_status":"In Progress","how_found":"Customer Reported"},"feedUrl":"https://trust.zscaler.com/rss-feed/incidents?_format=json","trustEnvironment":"Commercial","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-07-01T18:12:00.996Z","lastUpdated":"2026-07-10T06:07:00.158Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"major","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-06-30T02:50:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/rsmwp7jcy0pd","title":"Last Mile node LM - Lucca, IT - Wind3 offline","description":"<p> <small>Jun <var data-var='date'>29</var>, <var data-var='time'>21:18</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Lucca, IT - Wind3 will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Mon, 29 Jun 2026 21:18:15 +0000","link":"https://lmstatus.catchpoint.com/incidents/rsmwp7jcy0pd","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-29T21:18:00.000Z","resolved_at":null,"startTime":"2026-06-29T21:18:00.000Z","endTime":null,"updatedAt":"2026-06-29T21:18:00.000Z","location":"Lucca","country":"IT","provider":"Wind3 offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-29T21:18:00.000Z","_parsedEndTime":null},{"title":"Private Application Session Timeouts with ZIA Inspection Enabled","link":"https://trust.zscaler.com/posts/30486","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 21:12:46 UTC</span></p><p>Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:59 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:01:15 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:04:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","pubDate":"Thu, 02 Jul 2026 20:35:16 GMT","guid":"30486 at https://trust.zscaler.com","id":"30486","clouds":["zscaler.net","zscalertwo.net","zscloud.net","zscalerthree.net"],"updates":[{"time":"Thu, 02 Jul 2026 21:12:46 UTC","update":"Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:59 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:01:15 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:04:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":[{"time":"Fri, 10 Jul 2026 06:04:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"root_cause":"","startTime":"Mon, 29 Jun 2026 13:00:00 GMT","endTime":null,"eventType":"Service Degradation","customerImpact":"A limited subset of customers using ZPA with ZIA Inspection enabled for certain private application traffic may experience connection timeouts or dropped sessions for SSH and other long-lived, non-HTTP private application sessions inspected by ZIA.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":{"name":"Recent incident","domain":"https://trust.zscaler.com"},"current_status":"In Progress","originalData":{"id":"30486","title":"Private Application Session Timeouts with ZIA Inspection Enabled","clouds":"[Circular Reference]","link":"https://trust.zscaler.com/posts/30486","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 21:12:46 UTC</span></p><p>Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:59 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:01:15 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:04:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","updates":[{"time":"Thu, 02 Jul 2026 21:12:46 UTC","update":"Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:59 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:01:15 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:04:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Thu, 02 Jul 2026 20:35:16 GMT","resolved_date":null,"startTime":"Mon, 29 Jun 2026 13:00:00 GMT","endTime":"","eventType":"Service Degradation","customerImpact":"A limited subset of customers using ZPA with ZIA Inspection enabled for certain private application traffic may experience connection timeouts or dropped sessions for SSH and other long-lived, non-HTTP private application sessions inspected by ZIA.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":"[Circular Reference]","current_status":"In Progress","how_found":"Customer Reported"},"feedUrl":"https://trust.zscaler.com/rss-feed/incidents?_format=json","trustEnvironment":"Commercial","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-07-02T20:52:01.540Z","lastUpdated":"2026-07-10T06:07:00.158Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-06-29T13:00:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/3jrd2v3v31pw","title":"Last Mile node LM - Ciudad de México, MX - TotalPlay offline","description":"<p> <small>Jun <var data-var='date'>29</var>, <var data-var='time'>09:23</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Ciudad de México, MX - TotalPlay will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Mon, 29 Jun 2026 09:23:15 +0000","link":"https://lmstatus.catchpoint.com/incidents/3jrd2v3v31pw","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-29T09:23:00.000Z","resolved_at":null,"startTime":"2026-06-29T09:23:00.000Z","endTime":null,"updatedAt":"2026-06-29T09:23:00.000Z","location":"Ciudad de México","country":"MX","provider":"TotalPlay offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-29T09:23:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/v2y0tzxjlbvl","title":"Last Mile node LM - Lipa, PH - Converge offline","description":"<p> <small>Jun <var data-var='date'>26</var>, <var data-var='time'>05:58</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Lipa, PH - Converge will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Fri, 26 Jun 2026 05:58:43 +0000","link":"https://lmstatus.catchpoint.com/incidents/v2y0tzxjlbvl","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-26T05:58:00.000Z","resolved_at":null,"startTime":"2026-06-26T05:58:00.000Z","endTime":null,"updatedAt":"2026-06-26T05:58:00.000Z","location":"Lipa","country":"PH","provider":"Converge offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-26T05:58:00.000Z","_parsedEndTime":null},{"title":"Potential CC/BC ZIA Tunnel Flap with Plain UDP Configuration","link":"https://trust.zscaler.us/posts/12856","description":"Zscaler is currently investigating reports of issues with traffic forwarding on its zscalergov.net (FedRAMP Moderate), zscalerten.net (FedRAMP High) Cloud. ","pubDate":"Tue, 23 Jun 2026 21:42:12 GMT","guid":"12856 at https://trust.zscaler.us","id":"12856","clouds":["zscalergov.net (FedRAMP Moderate)","zscalerten.net (FedRAMP High)"],"updates":[],"latest_update":[],"root_cause":"","startTime":"Mon, 22 Jun 2026 21:42:03 GMT","endTime":null,"eventType":"Under Investigation","customerImpact":"Customers with CC/BC groups configured for plain UDP tunnels may experience ZIA tunnel instability (flapping).\r\nTunnels in this configuration may transition between up and down states, potentially causing intermittent connectivity loss for ZIA-bound traffic.","availableWorkaround":"<p>Customers are advised to <strong>reconfigure affected CC/BC groups to use encrypted tunnels (DTLS)</strong> instead of plain UDP. Moving to encrypted tunnels has been confirmed to restore stable ZIA traffic flow.</p><h6>Steps:</h6><ol><li data-list-item-id=\"ef932c92390c59e0d8b1a03ad83c4f3a9\">Identify CC/BC groups currently configured with plain UDP in the group configuration.</li><li data-list-item-id=\"efdaba05d9867137e0959d22ad6e88557\">Update the group tunnel configuration from <strong>UDP</strong> to <strong>DTLS</strong>.</li><li data-list-item-id=\"e751c45636cffc7e4202b0ba8d2b39e03\">Validate that ZIA traffic is passing as expected after the change.</li></ol>","nextUpdate":null,"summary":"Zscaler has identified a potential issue where Cloud Connector (CC) and Branch Connector (BC) ZIA tunnels may flap if the group configuration is set to use plain (unencrypted) UDP tunnels. Affected tunnels may go up or down intermittently, which can result in traffic disruption.","category":{"name":"Recent incident","domain":"https://trust.zscaler.us"},"current_status":"In Progress","originalData":{"id":"12856","title":"Potential CC/BC ZIA Tunnel Flap with Plain UDP Configuration","clouds":"[Circular Reference]","link":"https://trust.zscaler.us/posts/12856","description":"Zscaler is currently investigating reports of issues with traffic forwarding on its zscalergov.net (FedRAMP Moderate), zscalerten.net (FedRAMP High) Cloud. ","updates":[],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Tue, 23 Jun 2026 21:42:12 GMT","resolved_date":null,"startTime":"Mon, 22 Jun 2026 21:42:03 GMT","endTime":"","eventType":"Under Investigation","customerImpact":"Customers with CC/BC groups configured for plain UDP tunnels may experience ZIA tunnel instability (flapping).\r\nTunnels in this configuration may transition between up and down states, potentially causing intermittent connectivity loss for ZIA-bound traffic.","availableWorkaround":"<p>Customers are advised to <strong>reconfigure affected CC/BC groups to use encrypted tunnels (DTLS)</strong> instead of plain UDP. Moving to encrypted tunnels has been confirmed to restore stable ZIA traffic flow.</p><h6>Steps:</h6><ol><li data-list-item-id=\"ef932c92390c59e0d8b1a03ad83c4f3a9\">Identify CC/BC groups currently configured with plain UDP in the group configuration.</li><li data-list-item-id=\"efdaba05d9867137e0959d22ad6e88557\">Update the group tunnel configuration from <strong>UDP</strong> to <strong>DTLS</strong>.</li><li data-list-item-id=\"e751c45636cffc7e4202b0ba8d2b39e03\">Validate that ZIA traffic is passing as expected after the change.</li></ol>","nextUpdate":"","summary":"Zscaler has identified a potential issue where Cloud Connector (CC) and Branch Connector (BC) ZIA tunnels may flap if the group configuration is set to use plain (unencrypted) UDP tunnels. Affected tunnels may go up or down intermittently, which can result in traffic disruption.","category":"[Circular Reference]","current_status":"In Progress","how_found":"Customer Reported"},"feedUrl":"https://trust.zscaler.us/rss-feed/incidents?_format=json","trustEnvironment":"Government","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-06-29T16:34:49.187Z","lastUpdated":"2026-06-29T16:34:49.187Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","_parsedIsResolved":false,"_parsedStartTime":"2026-06-22T21:42:03.000Z","_parsedEndTime":null},{"id":"d2gls1bq9csz","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Johannesburg</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-06-17T23:12:56.780Z","link":"https://stspg.io/xzyvc4hjn9fj","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-17T23:12:56.780Z","resolved_at":null,"startTime":"2026-06-17T23:12:56.780Z","endTime":null,"updatedAt":"2026-06-17T23:12:56.784Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"pryzc1frc4gp","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Johannesburg</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"d2gls1bq9csz","created_at":"2026-06-17T23:12:56.780Z","updated_at":"2026-06-17T23:12:56.780Z","display_at":"2026-06-17T23:12:56.780Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"d2gls1bq9csz","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-06-17T23:12:56.780Z","_parsedEndTime":null},{"id":"20004131","incidentId":"20004131","title":"coreService Degradation impacting multiple APAC instances (CS316-CS321)","description":"","pubDate":"2026-06-17T14:43:00.000Z","link":"https://status.salesforce.com/incidents/20004131","status":"Ongoing","impact":"minor","type":"Degradation","isResolved":false,"created_at":"2026-06-17T14:43:00.000Z","resolved_at":null,"startTime":"2026-06-17T14:43:00.000Z","endTime":null,"updatedAt":"2026-06-18T20:53:44.567Z","affectedComponents":["coreService","CS316","CS317","CS318","CS319","CS320","CS321"],"serviceKeys":["coreService"],"instanceKeys":["CS316","CS317","CS318","CS319","CS320","CS321"],"enhancedInstanceKeys":[{"key":"CS316","location":"APAC","city":null,"stateName":null,"stateCode":null,"countryName":null,"countryCode":null,"environment":"sandbox","status":"OK","isActive":true,"releaseVersion":"Summer '26 Patch 10.1","maintenanceWindow":"Saturdays 15:00 – 19:00 UTC"},{"key":"CS317","location":"APAC","city":null,"stateName":null,"stateCode":null,"countryName":null,"countryCode":null,"environment":"sandbox","status":"OK","isActive":true,"releaseVersion":"Summer '26 Patch 10.1","maintenanceWindow":"Saturdays 15:00 – 19:00 UTC"},{"key":"CS318","location":"APAC","city":null,"stateName":null,"stateCode":null,"countryName":null,"countryCode":null,"environment":"sandbox","status":"OK","isActive":true,"releaseVersion":"Summer '26 Patch 10.1","maintenanceWindow":"Saturdays 15:00 – 19:00 UTC"},{"key":"CS319","location":"APAC","city":null,"stateName":null,"stateCode":null,"countryName":null,"countryCode":null,"environment":"sandbox","status":"OK","isActive":true,"releaseVersion":"Summer '26 Patch 10.1","maintenanceWindow":"Saturdays 15:00 – 19:00 UTC"},{"key":"CS320","location":"APAC","city":null,"stateName":null,"stateCode":null,"countryName":null,"countryCode":null,"environment":"sandbox","status":"OK","isActive":true,"releaseVersion":"Summer '26 Patch 10.1","maintenanceWindow":"Saturdays 15:00 – 19:00 UTC"},{"key":"CS321","location":"APAC","city":null,"stateName":null,"stateCode":null,"countryName":null,"countryCode":null,"environment":"sandbox","status":"OK","isActive":true,"releaseVersion":"Summer '26 Patch 10.1","maintenanceWindow":"Saturdays 15:00 – 19:00 UTC"}],"incidentImpacts":[{"id":20004447,"startTime":"2026-06-17T14:43:00.000Z","endTime":null,"type":"featurePerfDegradation","severity":"minor","createdAt":"2026-06-18T20:53:44.560Z","updatedAt":"2026-06-18T20:53:44.565Z","startTimeCreatedAt":"2026-06-18T20:53:44.560Z","startTimeModifiedAt":null,"endTimeCreatedAt":null,"endTimeModifiedAt":null}],"timeline":[{"title":"Degradation Started","content":"featurePerfDegradation","createdAt":"2026-06-18T20:53:44.560Z","updatedAt":null,"entryType":"impact_start","startTime":"2026-06-17T14:43:00.000Z","sourceId":4447,"sourceType":"impact","impactStartTime":"2026-06-18T20:53:44.560Z"}],"guid":"20004131","incidentHistory":[{"eventType":"Update","description":"We’re investigating an issue impacting multiple sandbox instances, where some customers may experience difficulties accessing some files uploaded to long-term file storage. We’ve identified this is linked to an issue with our third-party infrastructure provider, and they’re actively working to restore their services. Our team remains fully engaged and is collaborating closely with the vendor to restore the services as quickly as possible.\n\nWe're actively monitoring the recovery and will share the next update as soon as new information is available","postedAt":"5:10 pm EDT, Jun 18 2026","lastUpdated":"5:10 pm EDT, Jun 18 2026"},{"eventType":"Update","description":"Restoration efforts with our third-party infrastructure provider continue to move forward. Current information on restoration timelines, milestones, and permanent remediation suggests that completion is expected within several weeks. The impact is limited to sandbox environments, and production services remain unaffected.\n\nWe'll provide additional updates as significant developments occur or sooner if new information becomes available.","postedAt":"3:18 pm EDT, Jun 25 2026","lastUpdated":"3:18 pm EDT, Jun 25 2026"},{"eventType":"Update","description":"We continue to make progress toward restoring services and remain in close coordination with our third-party infrastructure provider as recovery efforts continue. The impact remains limited to customers with sandbox environments on a subset of instances, and there is no impact to production environments.\nWe'll provide further updates upon significant developments or sooner as new information becomes available.","postedAt":"2:15 am EDT, Jun 24 2026","lastUpdated":"2:15 am EDT, Jun 24 2026"},{"eventType":"Update","description":"We continue to make progress to restore services. We remain in close coordination with our third-party infrastructure provider and are actively working toward a resolution.\nPlease note that the impact remains limited to customers with sandbox environments on a subset of instances, and there is no impact to production environments. \n\nWe will provide an update within 24 hours or sooner as new information becomes available.","postedAt":"12:54 am EDT, Jun 23 2026","lastUpdated":"12:54 am EDT, Jun 23 2026"},{"eventType":"Update","description":"We continue to make steady progress in restoring services and remain closely engaged with our third-party infrastructure provider. The impact is limited to customers with sandbox environments on a subset of instances. Production environments remain unaffected.\n\nWe will provide additional updates as significant developments occur or sooner if new information becomes available.","postedAt":"11:20 pm EDT, Jun 24 2026","lastUpdated":"11:20 pm EDT, Jun 24 2026"},{"eventType":"Update","description":"Our restoration efforts with our third-party infrastructure provider are progressing. A temporary solution to restore power to the affected data center is being developed, with an estimated target of mid-July 2026 to restore customer access and services. A permanent repair requiring replacement of damaged electrical components is also underway and will involve a longer timeline. The impact remains limited to sandbox environments, and production services continue to be unaffected. We will provide an update as significant developments occur or sooner if new information becomes available.","postedAt":"10:46 pm EDT, Jul 07 2026","lastUpdated":"10:46 pm EDT, Jul 07 2026"},{"eventType":"Feature Degradation Began","timestamp":"10:43 am EDT, Jun 17","description":"There’s a Salesforce service feature degradation. During a feature degradation, some features are unavailable or run at less than optimal performance. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.","postedAt":"4:53 pm EDT, Jun 18 2026"},{"eventType":"Update","description":"We remain fully engaged and are working in close coordination with the vendor to restore services as quickly as possible. We will continue to monitor the situation and provide an update as soon as new information becomes available.","postedAt":"1:14 am EDT, Jun 19 2026","lastUpdated":"1:14 am EDT, Jun 19 2026"}],"historyCount":8,"enhancedInfo":{"status":"Ongoing","impactedInstances":"CS316, CS317, CS318, CS319, CS320, CS321","impactedServices":"Core Service","startTime":"2:43 pm UTC, Jun 17","endTime":"-","duration":"3 weeks, 3 days"},"metadataScrapedAt":"2026-07-11T21:35:12.952Z","metadataLastUpdated":"2026-07-11T21:35:13.017Z","url":"https://status.salesforce.com/incidents/20004131","vendor":"Salesforce","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"salesforce","_parsedIsResolved":false,"_parsedStartTime":"2026-06-17T14:43:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/6d8cp25cb73c","title":"Last Mile node LM - Stockholm, SE - Comhem AB offline","description":"<p> <small>Jun <var data-var='date'>16</var>, <var data-var='time'>18:26</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Stockholm, SE - Comhem AB will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Tue, 16 Jun 2026 18:26:38 +0000","link":"https://lmstatus.catchpoint.com/incidents/6d8cp25cb73c","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-16T18:26:00.000Z","resolved_at":null,"startTime":"2026-06-16T18:26:00.000Z","endTime":null,"updatedAt":"2026-06-16T18:26:00.000Z","location":"Stockholm","country":"SE","provider":"Comhem AB offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-16T18:26:00.000Z","_parsedEndTime":null},{"id":"https://confluence.status.atlassian.com/incidents/13dv3crwm8kf","title":"Degraded performance with Confluence Cloud","description":"<p> <small>Jun <var data-var='date'>12</var>, <var data-var='time'>08:34</var> UTC</small><br> <strong>Investigating</strong> - Users are experiencing degraded performance with view content, create and edit functionality on Confluence Cloud primarily in the EU region.<br /><br />Our teams are actively working to identify the root cause of the issue. We will share additional updates in next 2 hours or sooner as more information is available. </p>","pubDate":"2026-06-12T08:34:01.000Z","link":"https://confluence.status.atlassian.com/incidents/13dv3crwm8kf","status":"investigating","impact":"none","isResolved":false,"created_at":"2026-06-12T08:34:01.000Z","resolved_at":null,"started_at":null,"startTime":"2026-06-12T08:34:01.000Z","endTime":null,"updatedAt":"2026-06-12T08:34:01.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"https://confluence.status.atlassian.com/incidents/13dv3crwm8kf","originalData":{"title":"Degraded performance with Confluence Cloud","description":"<p> <small>Jun <var data-var='date'>12</var>, <var data-var='time'>08:34</var> UTC</small><br> <strong>Investigating</strong> - Users are experiencing degraded performance with view content, create and edit functionality on Confluence Cloud primarily in the EU region.<br /><br />Our teams are actively working to identify the root cause of the issue. We will share additional updates in next 2 hours or sooner as more information is available. </p>","pubDate":"Fri, 12 Jun 2026 08:34:01 +0000","link":"https://confluence.status.atlassian.com/incidents/13dv3crwm8kf","guid":"https://confluence.status.atlassian.com/incidents/13dv3crwm8kf","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://confluence.status.atlassian.com/history.rss","firstSeen":"2026-06-12T08:36:00.806Z","lastUpdated":"2026-06-12T08:36:00.806Z","_productName":"Confluence","source":"atlassian-rss"},"source":"api","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","vendorId":"atlassian","vendor":"Atlassian","_parsedIsResolved":false,"_parsedStartTime":"2026-06-12T08:34:01.000Z","_parsedEndTime":null},{"id":"betterstack-status-report-919822","guid":"betterstack-status-report-919822","title":"Data serving slowness in Asia region","description":"We are experiencing slowness on large file downloads in Asia region since 7AM UTC. This only affects downloads via the huggingface CLI. Root cause identified and mitigation in progress.","pubDate":"2026-06-10T07:00:00.000Z","link":"https://status.huggingface.co/incident/919822","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-10T07:00:00.000Z","resolved_at":null,"started_at":"2026-06-10T07:00:00.000Z","startTime":"2026-06-10T07:00:00.000Z","endTime":null,"updatedAt":"2026-06-10T07:00:00.000Z","incidentUpdates":[{"body":"We are experiencing slowness on large file downloads in Asia region since 7AM UTC. This only affects downloads via the huggingface CLI. Root cause identified and mitigation in progress.","created_at":"2026-06-10T07:00:00.000Z","status":"investigating"}],"affectedComponents":[{"name":"Data serving slowness in Asia region"}],"originalData":{"rssUpdates":[{"title":"Data serving slowness in Asia region","link":"https://status.huggingface.co/incident/919822","pubDate":"Wed, 10 Jun 2026 07:00:00 -0000","guid":"https://status.huggingface.co/incident/919822#5373e8e2d3ac1436fd34c0e6de53ad866f3140aa61335594e99c11e7d469034d","description":"We are experiencing slowness on large file downloads in Asia region since 7AM UTC. This only affects downloads via the huggingface CLI. Root cause identified and mitigation in progress.","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T11:22:00.675Z","lastUpdated":"2026-06-10T11:22:00.675Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":"919822"},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-06-10T07:00:00.000Z","_parsedEndTime":null},{"title":"We are investigating increased error rates for Route53 API calls - Amazon Route 53","link":"https://health.aws.amazon.com/health/status#/arn:aws:health:global::event/ROUTE53/AWS_ROUTE53_OPERATIONAL_ISSUE/AWS_ROUTE53_OPERATIONAL_ISSUE_E3CB7_F9ACB328F17","description":"We are investigating increased error rates for Route53 API calls.","pubDate":"2026-05-22T23:39:56.000Z","guid":"arn:aws:health:global::event/ROUTE53/AWS_ROUTE53_OPERATIONAL_ISSUE/AWS_ROUTE53_OPERATIONAL_ISSUE_E3CB7_F9ACB328F17","id":"arn:aws:health:global::event/ROUTE53/AWS_ROUTE53_OPERATIONAL_ISSUE/AWS_ROUTE53_OPERATIONAL_ISSUE_E3CB7_F9ACB328F17","status":"1","serviceName":"Amazon Route 53","regionName":"","originalData":{"date":"1779493196","arn":"arn:aws:health:global::event/ROUTE53/AWS_ROUTE53_OPERATIONAL_ISSUE/AWS_ROUTE53_OPERATIONAL_ISSUE_E3CB7_F9ACB328F17","region_name":null,"status":"1","service":"route53","service_name":"Amazon Route 53","summary":"We are investigating increased error rates for Route53 API calls","event_log":[{"summary":"We are investigating increased error rates for Route53 API calls","message":"We are investigating increased error rates for Route53 API calls.","status":1,"timestamp":1779493196}]},"startTime":"2026-05-22T23:39:56.000Z","created_at":"2026-05-22T23:39:56.000Z","feedType":"incidents","feedCategory":"general","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://health.aws.amazon.com/public/currentevents","firstSeen":"2026-05-22T23:45:01.515Z","lastUpdated":"2026-05-22T23:45:01.515Z","vendor":"Amazon","vendorId":"amazon","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-05-22T23:39:56.000Z","_parsedEndTime":null},{"id":"mg2wqlfm15m8","title":"Prisma Cloud [APP3]: Intermittent login issues","description":"Status: investigating\n\nWe are currently investigating this issue.","pubDate":"2026-05-08T20:51:12.555Z","link":"https://stspg.io/hxz2rl8c96wm","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-05-08T20:51:12.555Z","resolved_at":null,"startTime":"2026-05-08T20:51:12.555Z","endTime":null,"updatedAt":"2026-05-08T20:51:30.092Z","affectedComponents":["Americas - US - app3.prismacloud.io"],"incidentUpdates":[{"id":"l0gzpn1j6nws","status":"identified","body":"The issue has been identified and a fix is being implemented.","incident_id":"mg2wqlfm15m8","created_at":"2026-05-08T20:51:30.089Z","updated_at":"2026-05-08T20:51:30.089Z","display_at":"2026-05-08T20:51:30.089Z","affected_components":[{"code":"6mb2hg5dvyf5","name":"Prisma Cloud - Americas - US - app3.prismacloud.io","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"x7q2szqzfzxj","status":"investigating","body":"We are currently investigating this issue.","incident_id":"mg2wqlfm15m8","created_at":"2026-05-08T20:51:12.555Z","updated_at":"2026-05-08T20:51:12.555Z","display_at":"2026-05-08T20:51:12.555Z","affected_components":[{"code":"6mb2hg5dvyf5","name":"Prisma Cloud - Americas - US - app3.prismacloud.io","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"mg2wqlfm15m8","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-05-08T20:51:12.555Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","guid":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-05-01T21:49:20.000Z","link":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-05-01T21:49:20.000Z","resolved_at":null,"started_at":"2026-05-01T21:49:20.000Z","startTime":"2026-05-01T21:49:20.000Z","endTime":null,"updatedAt":"2026-05-01T21:49:20.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-05-01T21:49:20.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Fri, 01 May 2026 21:49:20 +0000","guid":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-06-10T01:53:42.040Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-05-01T21:49:20.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/32zpqvzfnrlp","title":"Last Mile node LM - Paris, FR - Orange Fiber offline","description":"<p><small>Apr <var data-var='date'>17</var>, <var data-var='time'>14:09</var> UTC</small><br><strong>Investigating</strong> - Catchpoint Last Mile node LM - Paris, FR - Orange Fiber will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available.</p>","pubDate":"Fri, 17 Apr 2026 14:09:09 +0000","link":"https://lmstatus.catchpoint.com/incidents/32zpqvzfnrlp","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-17T14:09:00.000Z","resolved_at":null,"startTime":"2026-04-17T14:09:00.000Z","endTime":null,"updatedAt":"2026-04-17T14:09:00.000Z","location":"Paris","country":"FR","provider":"Orange Fiber offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-04-17T14:09:00.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","guid":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-14T14:53:47.000Z","link":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-14T14:53:47.000Z","resolved_at":null,"started_at":"2026-04-14T14:53:47.000Z","startTime":"2026-04-14T14:53:47.000Z","endTime":null,"updatedAt":"2026-04-14T14:53:47.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-14T14:53:47.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Tue, 14 Apr 2026 14:53:47 +0000","guid":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-11T21:37:00.758Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-14T14:53:47.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","guid":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-14T14:38:56.000Z","link":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-14T14:38:56.000Z","resolved_at":null,"started_at":"2026-04-14T14:38:56.000Z","startTime":"2026-04-14T14:38:56.000Z","endTime":null,"updatedAt":"2026-04-14T14:38:56.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-14T14:38:56.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Tue, 14 Apr 2026 14:38:56 +0000","guid":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-11T21:37:00.758Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-14T14:38:56.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","guid":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-09T10:08:32.000Z","link":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-09T10:08:32.000Z","resolved_at":null,"started_at":"2026-04-09T10:08:32.000Z","startTime":"2026-04-09T10:08:32.000Z","endTime":null,"updatedAt":"2026-04-09T10:08:32.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-09T10:08:32.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Thu, 09 Apr 2026 10:08:32 +0000","guid":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-08T03:27:00.883Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-09T10:08:32.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","guid":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-09T00:33:29.000Z","link":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-09T00:33:29.000Z","resolved_at":null,"started_at":"2026-04-09T00:33:29.000Z","startTime":"2026-04-09T00:33:29.000Z","endTime":null,"updatedAt":"2026-04-09T00:33:29.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-09T00:33:29.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Thu, 09 Apr 2026 00:33:29 +0000","guid":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-07T03:57:00.627Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-09T00:33:29.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","guid":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-09T00:18:34.000Z","link":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-09T00:18:34.000Z","resolved_at":null,"started_at":"2026-04-09T00:18:34.000Z","startTime":"2026-04-09T00:18:34.000Z","endTime":null,"updatedAt":"2026-04-09T00:18:34.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-09T00:18:34.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Thu, 09 Apr 2026 00:18:34 +0000","guid":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-07T03:57:00.627Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-09T00:18:34.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","guid":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-08T23:43:32.000Z","link":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-08T23:43:32.000Z","resolved_at":null,"started_at":"2026-04-08T23:43:32.000Z","startTime":"2026-04-08T23:43:32.000Z","endTime":null,"updatedAt":"2026-04-08T23:43:32.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-08T23:43:32.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Wed, 08 Apr 2026 23:43:32 +0000","guid":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-07T03:57:00.627Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-08T23:43:32.000Z","_parsedEndTime":null},{"id":"tag:status.redhat.com,2005:Incident/28729618","title":"AWS Outage: me-central","description":"<p> <small>Mar <var data-var='date'> 4</var>, <var data-var='time'>04:55</var> UTC</small><br> <strong>Update</strong> - AWS continues to make progress on recovery efforts across multiple workstreams. From now on, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.<br /><br />AWS Status Page: https://health.aws.amazon.com/health/status </p> <p> <small>Mar <var data-var='date'> 3</var>, <var data-var='time'>10:21</var> UTC</small><br> <strong>Update</strong> - The outage is still ongoing on AWS side. The AWS Management Console is now operational, and AWS is recommending to retry operations where possible, although most of the underlying service are still offline. </p> <p> <small>Mar <var data-var='date'> 2</var>, <var data-var='time'>17:52</var> UTC</small><br> <strong>Update</strong> - ROSA clusters deployed in me-central-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation. </p> <p> <small>Mar <var data-var='date'> 2</var>, <var data-var='time'>13:37</var> UTC</small><br> <strong>Update</strong> - Availability Zones in the ME-CENTRAL-1 Region (mec1-az2, mec1-az3) have been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone. </p> <p> <small>Mar <var data-var='date'> 1</var>, <var data-var='time'>14:26</var> UTC</small><br> <strong>Update</strong> - An Availability Zone in the ME-CENTRAL-1 Region (mec1-az2) has been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone. </p> <p> <small>Mar <var data-var='date'> 1</var>, <var data-var='time'>14:02</var> UTC</small><br> <strong>Identified</strong> - ROSA clusters degraded in me-central<br /><br />AWS Status Page: https://health.aws.amazon.com/health/status </p>","pubDate":"2026-03-04T04:55:09Z","link":"https://status.redhat.com/incidents/0lhzm5zhtzrn","status":"identified","impact":"major","isResolved":false,"created_at":"2026-03-04T04:55:09Z","resolved_at":null,"startTime":"2026-03-04T04:55:09Z","endTime":null,"updatedAt":"2026-03-04T04:55:09Z","guid":"tag:status.redhat.com,2005:Incident/28729618","healthScoreSeverity":"major","healthScoreSeveritySource":"impact","vendorId":"redhat","vendor":"Red Hat","_parsedIsResolved":false,"_parsedStartTime":"2026-03-04T04:55:09.000Z","_parsedEndTime":null},{"id":"tag:status.redhat.com,2005:Incident/28740919","title":"AWS Outage: me-south","description":"<p> <small>Mar <var data-var='date'> 4</var>, <var data-var='time'>04:44</var> UTC</small><br> <strong>Update</strong> - The outage is still ongoing on the AWS side, and recovery efforts are ongoing. AWS is recommending customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region </p> <p> <small>Mar <var data-var='date'> 2</var>, <var data-var='time'>17:52</var> UTC</small><br> <strong>Update</strong> - ROSA clusters deployed in me-south-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation. </p> <p> <small>Mar <var data-var='date'> 2</var>, <var data-var='time'>07:22</var> UTC</small><br> <strong>Identified</strong> - ROSA clusters degraded in me-south due to a localized power issue in mes1-az2.<br />Customers are advised to schedule their workloads into another availability zone.<br /><br />AWS Status Page: https://health.aws.amazon.com/health/status </p>","pubDate":"2026-03-04T04:44:10Z","link":"https://status.redhat.com/incidents/sg4h4gt51xbw","status":"identified","impact":"major","isResolved":false,"created_at":"2026-03-04T04:44:10Z","resolved_at":null,"startTime":"2026-03-04T04:44:10Z","endTime":null,"updatedAt":"2026-03-04T04:44:10Z","guid":"tag:status.redhat.com,2005:Incident/28740919","healthScoreSeverity":"major","healthScoreSeveritySource":"impact","vendorId":"redhat","vendor":"Red Hat","_parsedIsResolved":false,"_parsedStartTime":"2026-03-04T04:44:10.000Z","_parsedEndTime":null},{"title":"Increased Error Rates - Bahrain - Multiple services","link":"https://health.aws.amazon.com/health/status#/arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","description":"We are providing an update on the ongoing service disruption. The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable. Customers should recover their resources in other Regions from remote backups. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.  ","pubDate":"2026-03-02T05:56:27.000Z","guid":"arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","id":"arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","status":"3","serviceName":"Multiple services","regionName":"Bahrain","originalData":{"date":"1772430987","arn":"arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","region_name":"Bahrain","status":"3","service":"multipleservices-me-south-1","service_name":"Multiple services","summary":"Increased Error Rates","event_log":[{"summary":"Increased connectivity issues and API Error Rates","message":"We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.","status":1,"timestamp":1772430987},{"summary":"Increased connectivity issues and API Error Rates","message":"We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. During this time, we are also experiencing delays in propagating DNS changes for Route53 to pops (Points of Presence) in ME-SOUTH-1.  Targeting new launches using RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected.","status":1,"timestamp":1772435343},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work on a localized power issue affecting a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. In the impacted Availability Zone, EC2 Instances, DB Instances, EBS Volumes, and other AWS Services are also experiencing elevated error rates and latencies for some workflows. As part of our recovery effort, we have shifted traffic away from the impacted Availability Zone for most services. We recommend customers utilize one of the other Availability Zones in the ME-SOUTH-1 Region, as existing instances in other AZs remain unaffected by this issue. We are actively working to restore power and connectivity, at which time we will begin recovering affected resources. Currently, we expect recovery to take many hours. We will provide an update by 2:30 AM PST, or sooner if we have additional information to share.","status":1,"timestamp":1772442207},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. At this time, some AWS services have shifted traffic away from the affected Availability Zone and are seeing recovery for their affected operations and workflows. EC2 Instances, EBS Volumes, and other resources impacted in the affected Availability Zone will require a longer recovery timeline. Power has not yet been restored to the affected Availability Zone. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or launch replacement resources in one of the unaffected Availability Zones or an alternate Region. In parallel, we are actively working on reducing the error rates and latencies that some customers are experiencing with EC2 APIs. For now, we recommend continuing to retry any failed API requests. We will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.","status":1,"timestamp":1772448060},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work toward restoring power in the impacted Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. Meanwhile, EC2 instance and networking APIs have been restored for the other Availability Zones. Additionally, we have made improvements to the availability of RDS multi-AZ databases while operating with the impaired Availability Zone. These improvements will help customers create database exports to preserve data, and we recommend customers with databases in the affected Availability Zone consider creating exports as a precautionary measure. EC2 Instances, EBS Volumes, and other resources impacted in the affected Availability Zone will require a longer recovery timeline, as power has not yet been restored. We are expecting recovery to take at least a day, as it requires repair of facilities, cooling and power systems, coordination with local authorities, and careful assessment to ensure the safety of our operators. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. We will provide an update by 11:00 AM PST on March 2, or sooner if we have additional information to share.","status":1,"timestamp":1772461399},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We currently expect our recovery efforts to take at least a day. Our current guidance regarding immediate recovery remains unchanged from our previous update. Customers are able to disassociate Elastic IP addresses from resources in the affected Availability Zone and associate those with resources in the unaffected Availability Zones. This can be done by specifying --allow-reassociation when attempting to associate the Elastic IP to the new resource. We will provide you with further updates by 2:00 PM PST or sooner if new information becomes available.","status":1,"timestamp":1772477520},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue to advise customers to launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. At this time we recommend that customers that are capable of backing up data outside of the region consider doing so. You can view the current status of affected AWS services below. We will provide you with another update by 7:00 PM PST, or sooner if we have additional information to share.","status":1,"timestamp":1772490547},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.\n\nIn the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.\n\nIn parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We recommend that customers with workloads running in the Middle East consider taking action now to backup data and potentially migrate your workloads to alternate AWS Regions. We recommend customers exercise their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 9:00 PM PST on March 2, 2026, or sooner if new information becomes available.","status":1,"timestamp":1772497351},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. AWS infrastructure is designed to be highly resilient, but given the uncertainty of the current situation, we encourage our customers to replicate Amazon S3 and critical data from the ME-SOUTH-1 Region to another AWS Region. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 3 at 3:00 AM PST, or sooner if new information becomes available. \n\nFor more information on Cross-Region Replication, refer [1]. For more information on S3 Batch Replication, see [2]. For a simple script to quickly set up and start S3 Replication, see [3]. If you have questions or concerns, please contact AWS Support [4].\n\n[1] <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html\">https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html</a>\n[2] <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html\">https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html</a>\n[3] <a href=\"https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py\">https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py</a>\n[4] <a href=\"https://aws.amazon.com/support\">https://aws.amazon.com/support</a>","status":1,"timestamp":1772519220},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. The overall state of the region remains largely unchanged from our previous update. At this time, we have no updated guidance on expected timelines for fully restoring power and connectivity. We are taking all necessary steps to support the recovery process. While progress is being made, significant work remains before full restoration is complete. \n\nGiven the ongoing uncertainty, we encourage customers to replicate their Amazon S3 data and other critical data from the ME-SOUTH-1 Region to another AWS Region, using the guidance provided in our previous update. We will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 6:00 AM PST on March 3, or sooner if new information becomes available.","status":1,"timestamp":1772536238},{"summary":"Increased Connectivity Issues and API Error Rates","message":"Recovery efforts in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region are ongoing, with the situation remaining consistent with our last update. We have no change to expected timelines for fully restoring power and connectivity. While progress is being made, significant work remains before full restoration is complete. We continue to recommend customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region.\n\nGiven the extended nature of this event, we continue to encourage customers to replicate Amazon S3 data and other critical workloads from ME-SOUTH-1 to another AWS Region using the guidance shared previously. We will provide our next update by 12:00 PM PST on March 3, or sooner if conditions change.","status":1,"timestamp":1772546577},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.\n\nWe continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.","status":1,"timestamp":1772556000},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We are providing an update on the ongoing service disruption. The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable. Customers should recover their resources in other Regions from remote backups. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.  ","status":3,"timestamp":1777532831}],"impacted_services":{"resourcegroups-me-south-1":{"service_name":"AWS Resource Groups","current":"3","max":"3"},"codepipeline-me-south-1":{"service_name":"AWS CodePipeline","current":"3","max":"3"},"rds-me-south-1":{"service_name":"Amazon Relational Database Service","current":"3","max":"3"},"fargate-me-south-1":{"service_name":"AWS Fargate","current":"3","max":"3"},"awswaf-me-south-1":{"service_name":"AWS WAF","current":"3","max":"3"},"datasync-me-south-1":{"service_name":"AWS DataSync","current":"3","max":"3"},"ecr-me-south-1":{"service_name":"Amazon Elastic Container Registry","current":"3","max":"3"},"lakeformation-me-south-1":{"service_name":"AWS Lake Formation","current":"3","max":"3"},"lambda-me-south-1":{"service_name":"AWS Lambda","current":"3","max":"3"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"firehose-me-south-1":{"service_name":"Amazon Kinesis Firehose","current":"3","max":"3"},"redshift-me-south-1":{"service_name":"Amazon Redshift","current":"3","max":"3"},"sagemaker-me-south-1":{"service_name":"Amazon SageMaker","current":"3","max":"3"},"kafka-me-south-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"3","max":"3"},"transcribe-me-south-1":{"service_name":"Amazon Transcribe","current":"3","max":"3"},"eks-me-south-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"3","max":"3"},"transitgateway-me-south-1":{"service_name":"AWS Transit Gateway","current":"3","max":"3"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"cognito-me-south-1":{"service_name":"Amazon Cognito","current":"3","max":"3"},"cloudshell-me-south-1":{"service_name":"AWS CloudShell","current":"3","max":"3"},"kms-me-south-1":{"service_name":"AWS Key Management Service","current":"3","max":"3"},"emr-me-south-1":{"service_name":"Amazon Elastic MapReduce","current":"3","max":"3"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"ecs-me-south-1":{"service_name":"Amazon Elastic Container Service","current":"3","max":"3"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"1"},"controltower-me-south-1":{"service_name":"AWS Control Tower","current":"3","max":"3"},"fsx-me-south-1":{"service_name":"Amazon FSx","current":"3","max":"3"},"emrserverless-me-south-1":{"service_name":"Amazon EMR Serverless","current":"3","max":"3"},"sns-me-south-1":{"service_name":"Amazon Simple Notification Service","current":"3","max":"3"},"privatelink-me-south-1":{"service_name":"AWS VPCE PrivateLink","current":"3","max":"3"},"elasticsearch-me-south-1":{"service_name":"Amazon OpenSearch Service","current":"3","max":"3"},"elb-me-south-1":{"service_name":"Amazon Elastic Load Balancing","current":"3","max":"3"},"cloudtrail-me-south-1":{"service_name":"AWS CloudTrail","current":"3","max":"3"},"management-console":{"service_name":"AWS Management Console","current":"0","max":"2"},"natgateway-me-south-1":{"service_name":"AWS NAT Gateway","current":"3","max":"3"},"resourcegroupstaggingapi-me-south-1":{"service_name":"AWS Resource Groups Tagging API","current":"3","max":"3"},"cloud9-me-south-1":{"service_name":"AWS Cloud9","current":"3","max":"3"},"scheduler-me-south-1":{"service_name":"Amazon EventBridge Scheduler","current":"3","max":"3"},"state-me-south-1":{"service_name":"AWS Step Functions","current":"3","max":"3"},"elasticfilesystem-me-south-1":{"service_name":"Amazon Elastic File System","current":"3","max":"3"},"cloudhsm-me-south-1":{"service_name":"AWS CloudHSM","current":"3","max":"3"},"cloudwatch-me-south-1":{"service_name":"Amazon CloudWatch","current":"3","max":"3"},"directoryservice-me-south-1":{"service_name":"AWS Directory Service","current":"3","max":"3"},"elasticbeanstalk-me-south-1":{"service_name":"AWS Elastic Beanstalk","current":"3","max":"3"},"glue-me-south-1":{"service_name":"AWS Glue","current":"3","max":"3"},"autoscaling-me-south-1":{"service_name":"Auto Scaling","current":"3","max":"3"},"awsiot-me-south-1":{"service_name":"AWS IoT Core","current":"3","max":"3"},"clientvpn-me-south-1":{"service_name":"AWS Client VPN","current":"3","max":"3"},"servicecatalog-me-south-1":{"service_name":"AWS Service Catalog","current":"3","max":"3"},"storagegateway-me-south-1":{"service_name":"AWS Storage Gateway","current":"3","max":"3"},"computeoptimizer-me-south-1":{"service_name":"AWS Compute Optimizer","current":"3","max":"3"},"kinesis-me-south-1":{"service_name":"Amazon Kinesis Data Streams","current":"3","max":"3"},"dms-me-south-1":{"service_name":"AWS Database Migration Service","current":"3","max":"3"},"awsiotdevicemanagement-me-south-1":{"service_name":"AWS IoT Device Management","current":"3","max":"3"},"networkfirewall-me-south-1":{"service_name":"AWS Network Firewall","current":"3","max":"3"},"inspector-me-south-1":{"service_name":"Amazon Inspector","current":"3","max":"3"},"resourceexplorer-me-south-1":{"service_name":"AWS Resource Explorer","current":"3","max":"3"},"ssmsap-me-south-1":{"service_name":"AWS Systems Manager for SAP","current":"3","max":"3"},"codedeploy-me-south-1":{"service_name":"AWS CodeDeploy","current":"3","max":"3"},"iamidentitycenter-me-south-1":{"service_name":"AWS IAM Identity Center","current":"3","max":"3"},"transfer-me-south-1":{"service_name":"AWS Transfer Family","current":"3","max":"3"},"vpnvpc-me-south-1":{"service_name":"AWS Site-to-Site VPN","current":"3","max":"3"},"events-me-south-1":{"service_name":"Amazon EventBridge","current":"3","max":"3"},"iotdevicedefender-me-south-1":{"service_name":"AWS IoT Device Defender","current":"3","max":"3"},"codebuild-me-south-1":{"service_name":"AWS CodeBuild","current":"3","max":"3"},"elasticache-me-south-1":{"service_name":"Amazon ElastiCache","current":"3","max":"3"},"appsync-me-south-1":{"service_name":"AWS AppSync","current":"3","max":"3"},"drs-me-south-1":{"service_name":"AWS Elastic Disaster Recovery","current":"3","max":"3"},"vpclattice-me-south-1":{"service_name":"Amazon VPC Lattice","current":"3","max":"3"},"cloudformation-me-south-1":{"service_name":"AWS CloudFormation","current":"3","max":"3"},"mq-me-south-1":{"service_name":"Amazon MQ","current":"3","max":"3"},"swf-me-south-1":{"service_name":"Amazon Simple Workflow Service","current":"3","max":"3"},"ec2-me-south-1":{"service_name":"Amazon Elastic Compute Cloud","current":"3","max":"3"}}},"startTime":"2026-03-02T05:56:27.000Z","created_at":"2026-03-02T05:56:27.000Z","feedType":"incidents","feedCategory":"general","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://health.aws.amazon.com/public/currentevents","firstSeen":"2026-03-16T04:03:38.328Z","lastUpdated":"2026-04-30T15:05:01.166Z","vendor":"Amazon","vendorId":"amazon","healthScoreSeverity":"critical","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-03-02T05:56:27.000Z","_parsedEndTime":null},{"title":"Increased Error Rates - UAE - Multiple services","link":"https://health.aws.amazon.com/health/status#/arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","description":"We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months. ","pubDate":"2026-03-01T12:51:25.000Z","guid":"arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","id":"arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","status":"3","serviceName":"Multiple services","regionName":"UAE","originalData":{"date":"1772369485","arn":"arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","region_name":"UAE","status":"3","service":"multipleservices-me-central-1","service_name":"Multiple services","summary":"Increased Error Rates","event_log":[{"summary":"Increased Error Rates","message":"We are investigating issues with AWS services in the ME-CENTRAL-1 Region.","status":1,"timestamp":1772369485},{"summary":"Increased Error Rates","message":"We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. Targeting new launches using RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected.","status":1,"timestamp":1772371152},{"summary":"Increased Error Rates","message":"We can confirm that a localized power issue has affected a single Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). EC2 Instances, DB Instances, EBS Volumes, and others resources are currently unavailable and will experience connectivity issues at this time. Other AWS Services are also experiencing error rates and latencies for some workflows. We have weighed away traffic for most services at this time. We recommend customers utilize one of the other Availability Zones in the ME-CENTRAL-1 Region at this time, as existing instances in other AZ's remain unaffected by this issue. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. We will provide an update by 7:15 AM PST, or sooner if we have additional information to share.","status":1,"timestamp":1772374140},{"summary":"Increased Error Rates","message":"We wanted to provide some additional information on the isolated power issue. At this time, most AWS Services have weighted away from the affected Availability Zone (mec1-az2) and are seeing recovery for their affected operations and workflows. For EC2 Instances, EBS Volumes, and other resources that are impacted in the affected Zone, we will have a longer tail of recovery. At this time, power has not yet been restored to the affected AZ. For now, we recommend continuing to retry any failed API requests. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources by launching replacement resources in one of the unaffected zones, or an alternate region. As of this time, recovery is still several hours away. We will provide an update by 8:30 AM PST, or sooner if we have additional information to share.","status":2,"timestamp":1772377753},{"summary":"Increased Error Rates","message":"We continue to work toward restoring power in the affected Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). In parallel, we are actively working on improving error rates and latencies that some customers are observing for EC2 Networking and EC2 Describe APIs. Due to increased demand in the unaffected Availability Zones, customers may experience longer than usual provisioning times or may need to retry requests for certain instance types, or pick an alternative instance type. We will provide an update by 10:30 AM PST, or sooner if we have additional information to share. ","status":2,"timestamp":1772384340},{"summary":"Increased Error Rates","message":"We want to provide some additional information on the power issue in a single Availability Zone in the ME-CENTRAL-1 Region. At around 4:30 AM PST, one of our Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire. The fire department shut off power to the facility and generators as they worked to put out the fire. We are still awaiting permission to turn the power back on, and once we have, we will ensure we restore power and connectivity safely. It will take several hours to restore connectivity to the impacted AZ. The other AZs in the region are functioning normally. Customers who were running their applications redundantly across the AZs are not impacted by this event. EC2 Instance launches will continue to be impaired in the impacted AZ. We recommend that customers continue to retry any failed API requests. If immediate recovery of an affected resource (EC2 Instance, EBS Volume, RDS DB Instance, etc.) is required, we recommend restoring from your most recent backup, by launching replacement resources in one of the unaffected zones, or an alternate AWS Region. We will provide an update by 12:30 PM PST, or sooner if we have additional information to share.","status":3,"timestamp":1772386871},{"summary":"Increased Error Rates","message":"We are aware that some customers are experiencing errors when calling EC2 APIs, specifically networking related APIs (AllocateAddress, AssociateAddress, DescribeRouteTable, DescribeNetworkInterfaces). We are actively working on multiple paths to mitigate these issues. For customers experiencing throttling errors on the AllocateAddress APIs, we recommend retrying any failed API requests. We are deploying a configuration change to mitigate the AssociateAddress API errors and expect recovery in the next few hours. DescribeRouteTable and DescribeNetworkInterfaces API calls without specifying zone, Interface or Instance IDs are expected to fail until we restore the impacted zone. We recommend customers to pass these IDs explicitly in these API requests. For customers that can, we recommend considering using alternate AWS Regions. We will provide another update by 3:30 PM PST, or sooner if we have more to share.","status":3,"timestamp":1772396043},{"summary":"Increased Error Rates","message":"We are seeing positive signs of recovery for many of the EC2 APIs, such as Describes and AllocateAddress. We recognize that customers are still experiencing errors when attempting to call the AssociateAddress API, and are unable to disassociate addresses from resources that are affected by the underlying power issue. We continue to work on multiple parallel paths to mitigate both of these issues. We recommend continuing to retry requests wherever possible. We expect our current mitigation efforts for these specific issues to complete within the the two to three hours. As we progress with these mitigation efforts, customers will observe higher success rates for these operations. Additionally, we are investigating ways to speed up these specific mitigation efforts, but are ensuring we do so safely. As of this time, power restoration is still several hours away. We will provide another update by 5:30 PM PST, or sooner if we have additional information to share.","status":3,"timestamp":1772404099},{"summary":"Increased Error Rates","message":"We are seeing significant signs of recovery for AssociateAddress requests, and continue to work toward fully mitigating this issue. This combined with the earlier recovery of the AllocateAddress API means customers can now successfully create and associate new network addresses in the unaffected AZs. Other AWS Services are also now observing sustained improvement as a result of the EC2 Networking APIs recovery. We are now focusing on implementing a change that will allow customers to Disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. We expect this specific mitigation to take another hour to complete. We do not have an ETA for power restoration at this time. For customers that can, we recommend using alternate Availability Zones or other AWS Regions where applicable. We will provide another update by 6:30 PM, or sooner if we have additional information to share.","status":3,"timestamp":1772411201},{"summary":"Increased Error Rates","message":"We confirm the recovery of the AssociateAddress API requests. We have also applied a change that enables customers to disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. With these mitigations, customers can now successfully create and associate new network addresses in the unaffected AZs as well as re-associate Elastic IPs from resources in the affected zone to resources in the unaffected zones. We still do not have an ETA for power restoration at this time. For customers that can, we recommend using alternate Availability Zones or other AWS Regions where applicable. We will provide another update by 10:00 PM, or sooner if we have additional information to share.","status":3,"timestamp":1772416907},{"summary":"Increased Error Rates","message":"We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.","status":3,"timestamp":1772431169},{"summary":"Increased Error Rates","message":"We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3). Customers are also experiencing increased EC2 APIs and instance launch errors for the remaining zone (mec1-az1). At this point it is not possible to launch new instances in the region, although existing instances should not be affected in mec1-az1. Other AWS Services, such as DynamoDB and S3 are also experiencing significant error rates and latencies. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. For customers that can, we recommend failing away to another AWS Region at this time. We will provide an update by 12:00 AM PST, or sooner if we have additional information to share.","status":3,"timestamp":1772433960},{"summary":"Increased Error Rates","message":"We continue to work on a localized power issue affecting multiple Availability Zones in the ME-CENTRAL-1 Region (mec1-az2 and mec1-az3). Customers are experiencing increased EC2 API errors and instance launch failures across the region, and it is not currently possible to launch new instances; existing instances in mec1-az1 should not be affected. Amazon DynamoDB and Amazon S3 are also experiencing significant error rates and elevated latencies. We are actively working to restore power and connectivity, after which we will begin recovery of affected resources; full recovery is still expected to be many hours away. We recommend that affected customers failover, and backup any critical data, to another AWS Region. We will provide an update by 2:00 AM PST, or sooner if the situation changes.","status":3,"timestamp":1772441520},{"summary":"Increased Error Rates","message":"We wanted to provide more information on Amazon S3 given that there are two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. Amazon S3 is a regional service and designed to withstand the total loss of a single Availability Zone while maintaining S3's durability and availability. When the mec1-az2 AZ was powered off at approximately 4:00 AM PST on Sunday, March 1, S3 continued to operate normally. As the second AZ became impaired, S3 error rates increased. With two Availability Zones significantly impacted, customers are seeing high failure rates for data ingest and egress. We strongly advise customers to update their applications to ingest S3 data to an alternate AWS Region. As soon as practically possible, we will begin the restoration of our two Availability Zones which will include a careful assessment of data health and any repair of storage if necessary.\n\nIn addition, we can confirm that the AWS Management Console and command line interface (CLI) are disrupted by the failure of two Availability Zones. We continue to work towards recovery across all services, and we will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.","status":3,"timestamp":1772448800},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We are expecting recovery to take at least a day, as it requires repair of facilities, cooling and power systems, coordination with local authorities, and careful assessment to ensure the safety of our operators. EC2, Amazon DynamoDB and other AWS Services continue to experience significant error rates and elevated latencies.\nWe recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Further, we strongly advise customers to update their applications to ingest S3 data to an alternate AWS Region. We will provide an update by 11:00 AM PST on March 2, or sooner if we have additional information to share.","status":3,"timestamp":1772461323},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. The impact is causing elevated errors rates for both the Management Console and CLI. Our current expectation is that recovery will take at least a day to complete. We continue to recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions. We will continue to provide periodic updates on recovery efforts. Our next update will be by 2:00 PM PST or sooner if new information becomes available.","status":3,"timestamp":1772474389},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We have partially restored access to the AWS Management Console, however, some pages will continue to load unsuccessfully until we have recovered core services and power. In parallel to the power and recovery efforts, we are working to restore access to tools and utilities to allow customers to backup and migrate their data. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue advising customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions. We will provide you with another update by 6:00 PM PST, or sooner if new information becomes available.","status":3,"timestamp":1772487370},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.\n\nIn the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.\n\nIn parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We recommend that customers with workloads running in the Middle East consider taking action now to backup data and potentially migrate your workloads to alternate AWS Regions. We recommend customers exercise their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 9:00 PM PST on March 2, 2026, or sooner if new information becomes available.","status":3,"timestamp":1772497188},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region with a focus on restoring functionality to foundational services. Since our last update we have made incremental progress in recovering the DynamoDB control plane which will not be visible to external customers but are required for the restoration of service. Similarly we have made progress with the S3 control plane. The recovery of these foundational services, when complete, will enable a broad range of dependent AWS services to recover. We still estimate that the recovery time is at least a day before we are able to fully restore power and connectivity. We will provide you with another update by March 3 2:00 AM PST, or sooner if new information becomes available.","status":3,"timestamp":1772514818},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged from our previous update. We continue to work closely with local authorities and are prioritizing the safety of our personnel throughout our recovery efforts. Teams continue to assess the damage to the affected facilities and are working to restore infrastructure impacted by the event.\n\nWith respect to Amazon S3, we are seeing improvement in PUT and LIST availability. We continue to work on improving GET error rates, but full recovery will be dependent on restoring the affected infrastructure, which our teams continue to work toward.\n\nFor Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery efforts. We have not yet seen meaningful improvement in DynamoDB availability, but expect conditions to improve over the coming hours as recovery work progresses.\n\nAmazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region. We will begin relaxing these throttles as soon as we have fully recovered our foundational services and have sufficient capacity to support new launches safely.\n\nThe AWS Management Console is now operational, though customers may continue to experience errors on certain pages and operations as the underlying services work through their recovery. We recommend customers continue to retry requests where possible.\n\nAWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and a number of other AWS services that were impacted by this event remain degraded. The availability of these services is dependent on the recovery of our foundational services — primarily Amazon S3 and Amazon DynamoDB — and we expect to see improvement across these services as that recovery progresses.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 5:00 AM PST on March 3, or sooner if new information becomes available.","status":3,"timestamp":1772528640},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged, though our teams continue to make progress on recovery efforts across multiple workstreams. \n\nFor Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. \n\nThe AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery. We recommend that customers continue to retry requests where possible. \n\nWe strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. \n\nWe will provide another update by March 3 at 10:00 AM PST, or sooner if new information becomes available. ","status":3,"timestamp":1772542694},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams.\n\nFor Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery.\n\nWith the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.\n\nWe continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.","status":3,"timestamp":1772554485},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months. ","status":3,"timestamp":1777533954}],"impacted_services":{"vpclattice-me-central-1":{"service_name":"Amazon VPC Lattice","current":"3","max":"3"},"iamidentitycenter-me-central-1":{"service_name":"AWS IAM Identity Center","current":"3","max":"3"},"rds-me-central-1":{"service_name":"Amazon Relational Database Service","current":"3","max":"3"},"cloudwatch-me-central-1":{"service_name":"Amazon CloudWatch","current":"3","max":"3"},"signin-me-central-1":{"service_name":"AWS Sign-In","current":"3","max":"3"},"endusermessaging-me-central-1":{"service_name":"AWS End User Messaging","current":"3","max":"3"},"fms-me-central-1":{"service_name":"AWS Firewall Manager","current":"3","max":"3"},"swf-me-central-1":{"service_name":"Amazon Simple Workflow Service","current":"3","max":"3"},"iotdevicedefender-me-central-1":{"service_name":"AWS IoT Device Defender","current":"3","max":"3"},"trafficmirroring-me-central-1":{"service_name":"Traffic Mirroring","current":"3","max":"3"},"natgateway-me-central-1":{"service_name":"AWS NAT Gateway","current":"3","max":"3"},"aps":{"service_name":"Amazon Managed Service for Prometheus","current":"3","max":"3"},"batch-me-central-1":{"service_name":"AWS Batch","current":"3","max":"3"},"datasync-me-central-1":{"service_name":"AWS DataSync","current":"3","max":"3"},"directconnect-me-central-1":{"service_name":"AWS Direct Connect","current":"3","max":"3"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"secretsmanager-me-central-1":{"service_name":"AWS Secrets Manager","current":"3","max":"3"},"emr-me-central-1":{"service_name":"Amazon Elastic MapReduce","current":"3","max":"3"},"fsx-me-central-1":{"service_name":"Amazon FSx","current":"3","max":"3"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"2"},"cloudtrail-me-central-1":{"service_name":"AWS CloudTrail","current":"3","max":"3"},"grafana":{"service_name":"Amazon Managed Grafana","current":"3","max":"3"},"vpc-me-central-1":{"service_name":"Amazon Virtual Private Cloud","current":"3","max":"3"},"resourcegroups-me-central-1":{"service_name":"AWS Resource Groups","current":"3","max":"3"},"verifiedaccess":{"service_name":"AWS Verified Access","current":"3","max":"3"},"resourcegroupstaggingapi-me-central-1":{"service_name":"AWS Resource Groups Tagging API","current":"3","max":"3"},"management-console":{"service_name":"AWS Management Console","current":"0","max":"3"},"s3-me-central-1":{"service_name":"Amazon Simple Storage Service","current":"3","max":"3"},"cloudhsm-me-central-1":{"service_name":"AWS CloudHSM","current":"3","max":"3"},"elasticsearch-me-central-1":{"service_name":"Amazon OpenSearch Service","current":"3","max":"3"},"cloudshell-me-central-1":{"service_name":"AWS CloudShell","current":"3","max":"3"},"amplify":{"service_name":"AWS Amplify","current":"3","max":"3"},"transfer-me-central-1":{"service_name":"AWS Transfer Family","current":"3","max":"3"},"elasticbeanstalk-me-central-1":{"service_name":"AWS Elastic Beanstalk","current":"3","max":"3"},"awswaf-me-central-1":{"service_name":"AWS WAF","current":"3","max":"3"},"emrserverless-me-central-1":{"service_name":"Amazon EMR Serverless","current":"3","max":"3"},"config-me-central-1":{"service_name":"AWS Config","current":"3","max":"3"},"ecs-me-central-1":{"service_name":"Amazon Elastic Container Service","current":"3","max":"3"},"kinesisanalytics-me-central-1":{"service_name":"Amazon Managed Service for Apache Flink","current":"3","max":"3"},"glue-me-central-1":{"service_name":"AWS Glue","current":"3","max":"3"},"reachabilityanalyzer":{"service_name":"Reachability Analyzer","current":"3","max":"3"},"security-ir-me-central-1":{"service_name":"AWS Security Incident Response","current":"3","max":"3"},"ssmsap-me-central-1":{"service_name":"AWS Systems Manager for SAP","current":"3","max":"3"},"eks-me-central-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"3","max":"3"},"resourceexplorer-me-central-1":{"service_name":"AWS Resource Explorer","current":"3","max":"3"},"elasticache-me-central-1":{"service_name":"Amazon ElastiCache","current":"3","max":"3"},"certificatemanager-me-central-1":{"service_name":"AWS Certificate Manager","current":"3","max":"3"},"awsiotdevicemanagement-me-central-1":{"service_name":"AWS IoT Device Management","current":"3","max":"3"},"neptune-db-me-central-1":{"service_name":"Amazon Neptune","current":"3","max":"3"},"docdb-me-central-1":{"service_name":"Amazon DocumentDB","current":"3","max":"3"},"state-me-central-1":{"service_name":"AWS Step Functions","current":"3","max":"3"},"inspector-me-central-1":{"service_name":"Amazon Inspector","current":"3","max":"3"},"controltower-me-central-1":{"service_name":"AWS Control Tower","current":"3","max":"3"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"servicecatalog-me-central-1":{"service_name":"AWS Service Catalog","current":"3","max":"3"},"kafka-me-central-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"3","max":"3"},"lakeformation-me-central-1":{"service_name":"AWS Lake Formation","current":"3","max":"3"},"licensemanager-me-central-1":{"service_name":"AWS License Manager","current":"3","max":"3"},"fargate-me-central-1":{"service_name":"AWS Fargate","current":"3","max":"3"},"ec2-me-central-1":{"service_name":"Amazon Elastic Compute Cloud","current":"3","max":"3"},"kms-me-central-1":{"service_name":"AWS Key Management Service","current":"3","max":"3"},"servicediscovery-me-central-1":{"service_name":"AWS Cloud Map","current":"3","max":"3"},"sts-me-central-1":{"service_name":"AWS Security Token Service","current":"3","max":"3"},"workspaces":{"service_name":"Amazon WorkSpaces","current":"3","max":"3"},"appconfig-me-central-1":{"service_name":"AWS AppConfig","current":"3","max":"3"},"clientvpn-me-central-1":{"service_name":"AWS Client VPN","current":"3","max":"3"},"redshift-me-central-1":{"service_name":"Amazon Redshift","current":"3","max":"3"},"firehose-me-central-1":{"service_name":"Amazon Kinesis Firehose","current":"3","max":"3"},"ipam-me-central-1":{"service_name":"Amazon VPC IP Address Manager","current":"3","max":"3"},"elb-me-central-1":{"service_name":"Amazon Elastic Load Balancing","current":"3","max":"3"},"scheduler-me-central-1":{"service_name":"Amazon EventBridge Scheduler","current":"3","max":"3"},"privatelink-me-central-1":{"service_name":"AWS VPCE PrivateLink","current":"3","max":"3"},"lambda-me-central-1":{"service_name":"AWS Lambda","current":"3","max":"3"},"sqs-me-central-1":{"service_name":"Amazon Simple Queue Service","current":"3","max":"3"},"mq-me-central-1":{"service_name":"Amazon MQ","current":"3","max":"3"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"elemental-me-central-1":{"service_name":"AWS Elemental","current":"3","max":"3"},"storagegateway-me-central-1":{"service_name":"AWS Storage Gateway","current":"3","max":"3"},"dynamodb-me-central-1":{"service_name":"Amazon DynamoDB","current":"3","max":"3"},"athena-me-central-1":{"service_name":"Amazon Athena","current":"3","max":"3"},"appsync-me-central-1":{"service_name":"AWS AppSync","current":"3","max":"3"},"kinesis-me-central-1":{"service_name":"Amazon Kinesis Data Streams","current":"3","max":"3"},"directoryservice-me-central-1":{"service_name":"AWS Directory Service","current":"3","max":"3"},"events-me-central-1":{"service_name":"Amazon EventBridge","current":"3","max":"3"},"dms-me-central-1":{"service_name":"AWS Database Migration Service","current":"3","max":"3"},"cognito-me-central-1":{"service_name":"Amazon Cognito","current":"3","max":"3"},"ec2systemsmanager-me-central-1":{"service_name":"AWS Systems Manager","current":"3","max":"3"},"imagebuilder-me-central-1":{"service_name":"EC2 Image Builder","current":"3","max":"3"},"drs-me-central-1":{"service_name":"AWS Elastic Disaster Recovery","current":"3","max":"3"},"glacier-me-central-1":{"service_name":"Amazon Glacier","current":"3","max":"3"},"transitgateway-me-central-1":{"service_name":"AWS Transit Gateway","current":"3","max":"3"},"cloudformation-me-central-1":{"service_name":"AWS CloudFormation","current":"3","max":"3"},"acm-pca-me-central-1":{"service_name":"AWS Private Certificate Authority","current":"3","max":"3"},"networkfirewall-me-central-1":{"service_name":"AWS Network Firewall","current":"3","max":"3"},"awsiot-me-central-1":{"service_name":"AWS IoT Core","current":"3","max":"3"},"computeoptimizer-me-central-1":{"service_name":"AWS Compute Optimizer","current":"3","max":"3"},"mgn-me-central-1":{"service_name":"AWS Application Migration Service","current":"3","max":"3"},"codedeploy-me-central-1":{"service_name":"AWS CodeDeploy","current":"3","max":"3"},"iamrolesanywhere-me-central-1":{"service_name":"AWS Identity and Access Management Roles Anywhere","current":"3","max":"3"},"securityhub-me-central-1":{"service_name":"AWS Security Hub","current":"3","max":"3"},"autoscaling-me-central-1":{"service_name":"Auto Scaling","current":"3","max":"3"},"backup-me-central-1":{"service_name":"AWS Backup","current":"3","max":"3"},"ecr-me-central-1":{"service_name":"Amazon Elastic Container Registry","current":"3","max":"3"},"codecommit-me-central-1":{"service_name":"AWS CodeCommit","current":"3","max":"3"},"guardduty-me-central-1":{"service_name":"Amazon GuardDuty","current":"3","max":"3"},"apigateway-me-central-1":{"service_name":"Amazon API Gateway","current":"3","max":"3"},"sagemaker-me-central-1":{"service_name":"Amazon SageMaker","current":"3","max":"3"},"vpnvpc-me-central-1":{"service_name":"AWS Site-to-Site VPN","current":"3","max":"3"},"elasticfilesystem-me-central-1":{"service_name":"Amazon Elastic File System","current":"3","max":"3"},"ses-me-central-1":{"service_name":"Amazon Simple Email Service","current":"3","max":"3"},"sns-me-central-1":{"service_name":"Amazon Simple Notification Service","current":"3","max":"3"},"codepipeline-me-central-1":{"service_name":"AWS CodePipeline","current":"3","max":"3"},"codebuild-me-central-1":{"service_name":"AWS CodeBuild","current":"3","max":"3"}}},"startTime":"2026-03-01T12:51:25.000Z","created_at":"2026-03-01T12:51:25.000Z","feedType":"incidents","feedCategory":"general","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://health.aws.amazon.com/public/currentevents","firstSeen":"2026-03-16T04:03:38.328Z","lastUpdated":"2026-04-30T15:05:01.166Z","vendor":"Amazon","vendorId":"amazon","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-03-01T12:51:25.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/w05fqn4qfdqp","title":"Last Mile node LM - Paris, FR - Orange ADSL offline","description":"<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>04:08</var> UTC</small><br><strong>Investigating</strong> - Catchpoint Last Mile node LM - Paris, FR - Orange ADSL will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available.</p>","pubDate":"Sun, 01 Mar 2026 04:08:16 +0000","link":"https://lmstatus.catchpoint.com/incidents/w05fqn4qfdqp","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-03-01T04:08:00.000Z","resolved_at":null,"startTime":"2026-03-01T04:08:00.000Z","endTime":null,"updatedAt":"2026-03-01T04:08:00.000Z","location":"Paris","country":"FR","provider":"Orange ADSL offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-03-01T04:08:00.000Z","_parsedEndTime":null},{"id":"805chf9k0rvx","title":"\"No asset scanned\" error on Connector health dashboard","description":"Status: identified\n\nWe've had an outage on the metrics which impacts Data Security > Dashboard > Connector health and Data Security > Application \"No. Asset Scanned...\"","pubDate":"2026-02-26T17:14:16.185Z","link":"https://stspg.io/58fyt27pycjd","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-02-26T17:14:16.185Z","resolved_at":null,"startTime":"2026-02-26T17:14:16.185Z","endTime":null,"updatedAt":"2026-02-26T17:14:33.788Z","affectedComponents":["SaaS API - North America","SaaS API - Singapore","SaaS API - Frankfurt","SaaS API - India","SaaS API - Australia","SaaS API - London","SaaS API - Japan"],"incidentUpdates":[{"id":"yj2f58pmlnsj","status":"identified","body":"We've had an outage on the metrics which impacts Data Security > Dashboard > Connector health and Data Security > Application \"No. Asset Scanned...\"","incident_id":"805chf9k0rvx","created_at":"2026-02-26T17:14:16.391Z","updated_at":"2026-02-26T17:14:16.391Z","display_at":"2026-02-26T17:14:16.391Z","affected_components":[{"code":"bnljkq76h9cy","name":"Data Security (SaaS Security API) - SaaS API - North America","old_status":"operational","new_status":"partial_outage"},{"code":"lbbl8wqdvz36","name":"Data Security (SaaS Security API) - SaaS API - Singapore","old_status":"operational","new_status":"partial_outage"},{"code":"kxy3h1vwnn9x","name":"Data Security (SaaS Security API) - SaaS API - Frankfurt","old_status":"operational","new_status":"partial_outage"},{"code":"w4d208jmwv95","name":"Data Security (SaaS Security API) - SaaS API - India","old_status":"operational","new_status":"partial_outage"},{"code":"h3wnt9g353kw","name":"Data Security (SaaS Security API) - SaaS API - Australia","old_status":"operational","new_status":"partial_outage"},{"code":"2wr4vkwbp1g8","name":"Data Security (SaaS Security API) - SaaS API - London","old_status":"operational","new_status":"partial_outage"},{"code":"5mbh3wj9xvz4","name":"Data Security (SaaS Security API) - SaaS API - Japan","old_status":"operational","new_status":"partial_outage"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"805chf9k0rvx","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-02-26T17:14:16.185Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/5e247026-cf08-4cdc-a1db-21a23e8c5f82","title":"Degraded Performance on LastPass Marketing Website","description":"[Resolved] Systems are operational and the incident is resolved","pubDate":"Wed, 29 Oct 2025 17:04:02 -0700","link":"https://status.lastpass.com/incidents/5e247026-cf08-4cdc-a1db-21a23e8c5f82","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 29 Oct 2025 17:04:02 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 29 Oct 2025 17:04:02 -0700","endTime":null,"updatedAt":"Wed, 29 Oct 2025 17:04:02 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/5e247026-cf08-4cdc-a1db-21a23e8c5f82","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2025-10-30T00:04:02.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/5095916e-b039-4758-9468-5256c8ba4337","title":"LastPass - Login issues for Lastpass","description":"[Resolved] On 04/19/2023 , from approximately 13:33 UTC until 13:56 UTC, a small subset of Lastpass users would have noticed a message \"unknown error occurred\" when trying to login to the application.  Our engineers have corrected the issue and we confirm that all services are functional.  We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.","pubDate":"Wed, 19 Apr 2023 08:17:43 -0700","link":"https://status.lastpass.com/incidents/5095916e-b039-4758-9468-5256c8ba4337","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 19 Apr 2023 08:17:43 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 19 Apr 2023 08:17:43 -0700","endTime":null,"updatedAt":"Wed, 19 Apr 2023 08:17:43 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/5095916e-b039-4758-9468-5256c8ba4337","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2023-04-19T15:17:43.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/768d9296-5a2a-4d37-8f8a-ebfe4f30e71d","title":"LastPass - Intermittent login failures","description":"[Resolved] On 11/06/2019, from 12:00 until 12:10 UTC, some LastPass users may have experienced intermittent authentication failures and errors while logging in. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize any future recurrences.","pubDate":"Wed, 06 Nov 2019 04:31:32 -0800","link":"https://status.lastpass.com/incidents/768d9296-5a2a-4d37-8f8a-ebfe4f30e71d","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 06 Nov 2019 04:31:32 -0800","resolved_at":null,"started_at":null,"startTime":"Wed, 06 Nov 2019 04:31:32 -0800","endTime":null,"updatedAt":"Wed, 06 Nov 2019 04:31:32 -0800","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/768d9296-5a2a-4d37-8f8a-ebfe4f30e71d","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2019-11-06T12:31:32.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/8696e49b-8d6e-40ae-8d30-1367ff7ab557","title":"LastPass - Issue with LastPass Identity","description":"[Resolved] On 10/30/2019, from 12:32 until 12:43 UTC, a subset of LastPass customers may have experienced transient errors and slowdowns with LastPass Identity. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize any future recurrences.","pubDate":"Wed, 30 Oct 2019 09:32:06 -0700","link":"https://status.lastpass.com/incidents/8696e49b-8d6e-40ae-8d30-1367ff7ab557","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 30 Oct 2019 09:32:06 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 30 Oct 2019 09:32:06 -0700","endTime":null,"updatedAt":"Wed, 30 Oct 2019 09:32:06 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/8696e49b-8d6e-40ae-8d30-1367ff7ab557","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"critical","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2019-10-30T16:32:06.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/4793ee31-fb7d-4b7f-80f5-79446d0ff889","title":"Connection Error (RESOLVED)","description":"[Resolved] The Network Operations Center resolved an issue with LastPass where some customers may have experienced intermittent errors when attempting to access LastPass.com from 4:50am - 5:12am ET.","pubDate":"Wed, 02 May 2018 05:41:51 -0700","link":"https://status.lastpass.com/incidents/4793ee31-fb7d-4b7f-80f5-79446d0ff889","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 02 May 2018 05:41:51 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 02 May 2018 05:41:51 -0700","endTime":null,"updatedAt":"Wed, 02 May 2018 05:41:51 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/4793ee31-fb7d-4b7f-80f5-79446d0ff889","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2018-05-02T12:41:51.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/763fc379-cead-4fe2-b744-98896e48c31e","title":"Server Not Available Error","description":"[Resolved] The intermittent connectivity issue should now be resolved and operating normally. \r\n \r\n We will keep monitoring the affected components to ensure full service.\r\n \r\n Our apologies again for any inconvenience caused, and thank you all for your patience.","pubDate":"Wed, 21 Feb 2018 09:15:31 -0800","link":"https://status.lastpass.com/incidents/763fc379-cead-4fe2-b744-98896e48c31e","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 21 Feb 2018 09:15:31 -0800","resolved_at":null,"started_at":null,"startTime":"Wed, 21 Feb 2018 09:15:31 -0800","endTime":null,"updatedAt":"Wed, 21 Feb 2018 09:15:31 -0800","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/763fc379-cead-4fe2-b744-98896e48c31e","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2018-02-21T17:15:31.000Z","_parsedEndTime":null}],"monitoring":[{"title":"ZDX Copilot Experiencing Degraded Performance for Entity-Based Questions","link":"https://trust.zscaler.com/posts/30651","description":"<div class=\"update-list update-1\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 20:03:56 UTC</span></p><p>We have identified the root cause of the issue and working on resolution.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 21:20:35 UTC</span></p><p>e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.</p></div>","pubDate":"Sat, 11 Jul 2026 19:43:42 GMT","guid":"30651 at https://trust.zscaler.com","id":"30651","clouds":["zdxcloud.net"],"updates":[{"time":"Sat, 11 Jul 2026 20:03:56 UTC","update":"We have identified the root cause of the issue and working on resolution.","status":"In-Progress"},{"time":"Sat, 11 Jul 2026 21:20:35 UTC","update":"e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.","status":"In-Progress"}],"latest_update":[{"time":"Sat, 11 Jul 2026 21:20:35 UTC","update":"We have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.","status":"In-Progress"}],"root_cause":"","startTime":"Sat, 11 Jul 2026 18:00:00 GMT","endTime":null,"eventType":"Under Investigation","customerImpact":"Customers using ZDX Copilot may see degraded performance when asking questions that involve users, devices, applications and other entities.","availableWorkaround":"","nextUpdate":"12 Jul 2026 04:00 UTC","summary":"","category":{"name":"Recent incident","domain":"https://trust.zscaler.com"},"current_status":"In Progress","originalData":{"id":"30651","title":"ZDX Copilot Experiencing Degraded Performance for Entity-Based Questions","clouds":"[Circular Reference]","link":"https://trust.zscaler.com/posts/30651","description":"<div class=\"update-list update-1\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 20:03:56 UTC</span></p><p>We have identified the root cause of the issue and working on resolution.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 21:20:35 UTC</span></p><p>e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.</p></div>","updates":[{"time":"Sat, 11 Jul 2026 20:03:56 UTC","update":"We have identified the root cause of the issue and working on resolution.","status":"In-Progress"},{"time":"Sat, 11 Jul 2026 21:20:35 UTC","update":"e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.","status":"In-Progress"}],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Sat, 11 Jul 2026 19:43:42 GMT","resolved_date":null,"startTime":"Sat, 11 Jul 2026 18:00:00 GMT","endTime":"","eventType":"Under Investigation","customerImpact":"Customers using ZDX Copilot may see degraded performance when asking questions that involve users, devices, applications and other entities.","availableWorkaround":"","nextUpdate":"12 Jul 2026 04:00 UTC","summary":"","category":"[Circular Reference]","current_status":"In Progress"},"feedUrl":"https://trust.zscaler.com/rss-feed/incidents?_format=json","trustEnvironment":"Commercial","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-07-11T20:02:00.246Z","lastUpdated":"2026-07-11T21:22:01.192Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-07-11T18:00:00.000Z","_parsedEndTime":null},{"id":"https://status.bigid.com/incidents/7n76jb4x1czb","title":"07-10-2026 Incident","description":"<p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>18:10</var> UTC</small><br> <strong>Monitoring</strong> - A fix has been implemented, and we are monitoring the results.<br /><br />We will provide the next update by 04:00 UTC. </p> <p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>17:39</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating performance degradation affecting one of our clusters.<br /><br />Our team is actively looking into the issue and will provide the next update by 20:00 UTC. </p>","pubDate":"2026-07-10T18:10:02.000Z","link":"https://status.bigid.com/incidents/7n76jb4x1czb","status":"monitoring","impact":"none","isResolved":false,"created_at":"2026-07-10T17:39:00.000Z","resolved_at":null,"started_at":"2026-07-10T17:39:00.000Z","startTime":"2026-07-10T17:39:00.000Z","endTime":null,"updatedAt":"2026-07-10T18:10:02.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.bigid.com/incidents/7n76jb4x1czb","originalData":{"title":"07-10-2026 Incident","description":"<p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>18:10</var> UTC</small><br> <strong>Monitoring</strong> - A fix has been implemented, and we are monitoring the results.<br /><br />We will provide the next update by 04:00 UTC. </p> <p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>17:39</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating performance degradation affecting one of our clusters.<br /><br />Our team is actively looking into the issue and will provide the next update by 20:00 UTC. </p>","pubDate":"Fri, 10 Jul 2026 18:10:02 +0000","link":"https://status.bigid.com/incidents/7n76jb4x1czb","guid":"https://status.bigid.com/incidents/7n76jb4x1czb","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.bigid.com/history.rss","firstSeen":"2026-07-10T17:44:00.720Z","lastUpdated":"2026-07-10T18:14:00.461Z","vendor":"BigID","source":"rss-feed"},"source":"rss-feed","vendor":"BigID","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"bigid","_parsedIsResolved":false,"_parsedStartTime":"2026-07-10T17:39:00.000Z","_parsedEndTime":null},{"id":"v45fs6q744nt","title":"Azure westeurope, southcentralus outage impacting Cloud NGFW Services.","description":"Status: monitoring\n\nWe have identified an issue with Azure affecting the Cloud NGFW westeurope and southcentralus regions. Customers may experience failures to during autoscaling and during deployment of new resources.\n\nCurrent Status: Azure is currently experiencing compute capacity issues within the regions. This is impacting our ability to scale out new virtual machines. \n\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. \n\nNext Update: Fri, July  11th, 01:00UTC","pubDate":"2026-07-07T18:06:04.984Z","link":"https://stspg.io/zfhnnrf4ksg7","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-07-07T18:06:04.984Z","resolved_at":null,"startTime":"2026-07-07T18:06:04.984Z","endTime":null,"updatedAt":"2026-07-10T09:21:36.435Z","affectedComponents":["australiaeast","australiasoutheast","canadacentral","centralus","eastasia","eastus","eastus2","northeurope","uksouth","ukwest","westeurope","westus","westus2","westus3","brazilsouth","japaneast","northcentralus","southeastasia","canadaeast","centralindia","francecentral","germanywestcentral","israelcentral","italynorth","japanwest","koreacentral","mexicocentral","newzealandnorth","norwayeast","southafricanorth","southcentralus","southindia","spaincentral","swedencentral","switzerlandnorth","switzerlandwest","uaenorth","westcentralus"],"incidentUpdates":[{"id":"7zckmylydfcs","status":"monitoring","body":"Azure is still working on recovery. We are continuously monitoring their progress.","incident_id":"v45fs6q744nt","created_at":"2026-07-10T09:16:24.296Z","updated_at":"2026-07-10T09:16:24.296Z","display_at":"2026-07-10T09:16:24.296Z","affected_components":[{"code":"nj5xnr1lyh1g","name":"Cloud NGFW for Azure - australiaeast","old_status":"operational","new_status":"operational"},{"code":"29jkdyh9zyqf","name":"Cloud NGFW for Azure - australiasoutheast","old_status":"operational","new_status":"operational"},{"code":"c179jwk1czjd","name":"Cloud NGFW for Azure - canadacentral","old_status":"operational","new_status":"operational"},{"code":"xpryk8b9yxdh","name":"Cloud NGFW for Azure - centralus","old_status":"operational","new_status":"operational"},{"code":"twl8v5dtbwq5","name":"Cloud NGFW for Azure - eastasia","old_status":"operational","new_status":"operational"},{"code":"nwh2fyy9xdf1","name":"Cloud NGFW for Azure - eastus","old_status":"operational","new_status":"operational"},{"code":"hbdk3yc4g006","name":"Cloud NGFW for Azure - eastus2","old_status":"operational","new_status":"operational"},{"code":"ztxqdqqcnyvf","name":"Cloud NGFW for Azure - northeurope","old_status":"operational","new_status":"operational"},{"code":"6tj8rj12yj9n","name":"Cloud NGFW for Azure - uksouth","old_status":"operational","new_status":"operational"},{"code":"q7rr14g803x4","name":"Cloud NGFW for Azure - ukwest","old_status":"operational","new_status":"operational"},{"code":"rmn0j5t26164","name":"Cloud NGFW for Azure - westeurope","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"dzrklwwcvqwd","name":"Cloud NGFW for Azure - westus","old_status":"operational","new_status":"operational"},{"code":"pr7frkm0nn8t","name":"Cloud NGFW for Azure - westus2","old_status":"operational","new_status":"operational"},{"code":"c61v8wxxk3dl","name":"Cloud NGFW for Azure - westus3","old_status":"operational","new_status":"operational"},{"code":"q441ddyb08d9","name":"Cloud NGFW for Azure - brazilsouth","old_status":"operational","new_status":"operational"},{"code":"q9n3z9r6f5hl","name":"Cloud NGFW for Azure - japaneast","old_status":"operational","new_status":"operational"},{"code":"1thk09f83tvq","name":"Cloud NGFW for Azure - northcentralus","old_status":"operational","new_status":"operational"},{"code":"372t6yz2h09m","name":"Cloud NGFW for Azure - southeastasia","old_status":"operational","new_status":"operational"},{"code":"zlhd8f97zdvs","name":"Cloud NGFW for Azure - canadaeast","old_status":"operational","new_status":"operational"},{"code":"44566lqf64l8","name":"Cloud NGFW for Azure - centralindia","old_status":"operational","new_status":"operational"},{"code":"vn81g46sd4nl","name":"Cloud NGFW for Azure - francecentral","old_status":"operational","new_status":"operational"},{"code":"x30qbkw3r7kh","name":"Cloud NGFW for Azure - germanywestcentral","old_status":"operational","new_status":"operational"},{"code":"q036sjp6t782","name":"Cloud NGFW for Azure - israelcentral","old_status":"operational","new_status":"operational"},{"code":"z8vl0b0gfrz1","name":"Cloud NGFW for Azure - italynorth","old_status":"operational","new_status":"operational"},{"code":"6jxgr5d17zxc","name":"Cloud NGFW for Azure - japanwest","old_status":"operational","new_status":"operational"},{"code":"fkg7zyvtyhvd","name":"Cloud NGFW for Azure - koreacentral","old_status":"operational","new_status":"operational"},{"code":"wmj90v8ybf8m","name":"Cloud NGFW for Azure - mexicocentral","old_status":"operational","new_status":"operational"},{"code":"dnthqvt3my77","name":"Cloud NGFW for Azure - newzealandnorth","old_status":"operational","new_status":"operational"},{"code":"rvyv5pq8yt51","name":"Cloud NGFW for Azure - norwayeast","old_status":"operational","new_status":"operational"},{"code":"cm5mnq16ds14","name":"Cloud NGFW for Azure - southafricanorth","old_status":"operational","new_status":"operational"},{"code":"nzfz4y4t2609","name":"Cloud NGFW for Azure - southcentralus","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"k0rv77zfscyn","name":"Cloud NGFW for Azure - southindia","old_status":"operational","new_status":"operational"},{"code":"08kf4wrjm0gk","name":"Cloud NGFW for Azure - spaincentral","old_status":"operational","new_status":"operational"},{"code":"n8vn15tcm77m","name":"Cloud NGFW for Azure - swedencentral","old_status":"operational","new_status":"operational"},{"code":"xs6wzpqghs2z","name":"Cloud NGFW for Azure - switzerlandnorth","old_status":"operational","new_status":"operational"},{"code":"0mzg05k0g61y","name":"Cloud NGFW for Azure - switzerlandwest","old_status":"operational","new_status":"operational"},{"code":"9py5w1vt566g","name":"Cloud NGFW for Azure - uaenorth","old_status":"operational","new_status":"operational"},{"code":"mqlsh01qn7k4","name":"Cloud NGFW for Azure - westcentralus","old_status":"operational","new_status":"operational"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"7whh642m1d4t","status":"monitoring","body":"Azure is still working on recovery. We are continuously monitoring their progress.","incident_id":"v45fs6q744nt","created_at":"2026-07-08T15:45:37.737Z","updated_at":"2026-07-08T15:45:37.737Z","display_at":"2026-07-08T15:45:37.737Z","affected_components":[{"code":"nj5xnr1lyh1g","name":"Cloud NGFW for Azure - australiaeast","old_status":"operational","new_status":"operational"},{"code":"29jkdyh9zyqf","name":"Cloud NGFW for Azure - australiasoutheast","old_status":"operational","new_status":"operational"},{"code":"c179jwk1czjd","name":"Cloud NGFW for Azure - canadacentral","old_status":"operational","new_status":"operational"},{"code":"xpryk8b9yxdh","name":"Cloud NGFW for Azure - centralus","old_status":"operational","new_status":"operational"},{"code":"twl8v5dtbwq5","name":"Cloud NGFW for Azure - eastasia","old_status":"operational","new_status":"operational"},{"code":"nwh2fyy9xdf1","name":"Cloud NGFW for Azure - eastus","old_status":"operational","new_status":"operational"},{"code":"hbdk3yc4g006","name":"Cloud NGFW for Azure - eastus2","old_status":"operational","new_status":"operational"},{"code":"ztxqdqqcnyvf","name":"Cloud NGFW for Azure - northeurope","old_status":"operational","new_status":"operational"},{"code":"6tj8rj12yj9n","name":"Cloud NGFW for Azure - uksouth","old_status":"operational","new_status":"operational"},{"code":"q7rr14g803x4","name":"Cloud NGFW for Azure - ukwest","old_status":"operational","new_status":"operational"},{"code":"rmn0j5t26164","name":"Cloud NGFW for Azure - westeurope","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"dzrklwwcvqwd","name":"Cloud NGFW for Azure - westus","old_status":"operational","new_status":"operational"},{"code":"pr7frkm0nn8t","name":"Cloud NGFW for Azure - westus2","old_status":"operational","new_status":"operational"},{"code":"c61v8wxxk3dl","name":"Cloud NGFW for Azure - westus3","old_status":"operational","new_status":"operational"},{"code":"q441ddyb08d9","name":"Cloud NGFW for Azure - brazilsouth","old_status":"operational","new_status":"operational"},{"code":"q9n3z9r6f5hl","name":"Cloud NGFW for Azure - japaneast","old_status":"operational","new_status":"operational"},{"code":"1thk09f83tvq","name":"Cloud NGFW for Azure - northcentralus","old_status":"operational","new_status":"operational"},{"code":"372t6yz2h09m","name":"Cloud NGFW for Azure - southeastasia","old_status":"operational","new_status":"operational"},{"code":"zlhd8f97zdvs","name":"Cloud NGFW for Azure - canadaeast","old_status":"operational","new_status":"operational"},{"code":"44566lqf64l8","name":"Cloud NGFW for Azure - centralindia","old_status":"operational","new_status":"operational"},{"code":"vn81g46sd4nl","name":"Cloud NGFW for Azure - francecentral","old_status":"operational","new_status":"operational"},{"code":"x30qbkw3r7kh","name":"Cloud NGFW for Azure - germanywestcentral","old_status":"operational","new_status":"operational"},{"code":"q036sjp6t782","name":"Cloud NGFW for Azure - israelcentral","old_status":"operational","new_status":"operational"},{"code":"z8vl0b0gfrz1","name":"Cloud NGFW for Azure - italynorth","old_status":"operational","new_status":"operational"},{"code":"6jxgr5d17zxc","name":"Cloud NGFW for Azure - japanwest","old_status":"operational","new_status":"operational"},{"code":"fkg7zyvtyhvd","name":"Cloud NGFW for Azure - koreacentral","old_status":"operational","new_status":"operational"},{"code":"wmj90v8ybf8m","name":"Cloud NGFW for Azure - mexicocentral","old_status":"operational","new_status":"operational"},{"code":"dnthqvt3my77","name":"Cloud NGFW for Azure - newzealandnorth","old_status":"operational","new_status":"operational"},{"code":"rvyv5pq8yt51","name":"Cloud NGFW for Azure - norwayeast","old_status":"operational","new_status":"operational"},{"code":"cm5mnq16ds14","name":"Cloud NGFW for Azure - southafricanorth","old_status":"operational","new_status":"operational"},{"code":"nzfz4y4t2609","name":"Cloud NGFW for Azure - southcentralus","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"k0rv77zfscyn","name":"Cloud NGFW for Azure - southindia","old_status":"operational","new_status":"operational"},{"code":"08kf4wrjm0gk","name":"Cloud NGFW for Azure - spaincentral","old_status":"operational","new_status":"operational"},{"code":"n8vn15tcm77m","name":"Cloud NGFW for Azure - swedencentral","old_status":"operational","new_status":"operational"},{"code":"xs6wzpqghs2z","name":"Cloud NGFW for Azure - switzerlandnorth","old_status":"operational","new_status":"operational"},{"code":"0mzg05k0g61y","name":"Cloud NGFW for Azure - switzerlandwest","old_status":"operational","new_status":"operational"},{"code":"9py5w1vt566g","name":"Cloud NGFW for Azure - uaenorth","old_status":"operational","new_status":"operational"},{"code":"mqlsh01qn7k4","name":"Cloud NGFW for Azure - westcentralus","old_status":"operational","new_status":"operational"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"xqdwjrrpcts7","status":"monitoring","body":"We have identified an issue with Azure affecting the Cloud NGFW westeurope and southcentralus regions. Customers may experience failures to during autoscaling and during deployment of new resources.\n\nCurrent Status: Azure is currently experiencing compute capacity issues within the regions. This is impacting our ability to scale out new virtual machines. \n\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. \n\nNext Update: Fri, July  11th, 01:00UTC","incident_id":"v45fs6q744nt","created_at":"2026-07-07T18:06:05.160Z","updated_at":"2026-07-10T09:21:36.412Z","display_at":"2026-07-07T18:06:05.000Z","affected_components":[{"code":"nj5xnr1lyh1g","name":"Cloud NGFW for Azure - australiaeast","old_status":"operational","new_status":"operational"},{"code":"29jkdyh9zyqf","name":"Cloud NGFW for Azure - australiasoutheast","old_status":"operational","new_status":"operational"},{"code":"c179jwk1czjd","name":"Cloud NGFW for Azure - canadacentral","old_status":"operational","new_status":"operational"},{"code":"xpryk8b9yxdh","name":"Cloud NGFW for Azure - centralus","old_status":"operational","new_status":"operational"},{"code":"twl8v5dtbwq5","name":"Cloud NGFW for Azure - eastasia","old_status":"operational","new_status":"operational"},{"code":"nwh2fyy9xdf1","name":"Cloud NGFW for Azure - eastus","old_status":"operational","new_status":"operational"},{"code":"hbdk3yc4g006","name":"Cloud NGFW for Azure - eastus2","old_status":"operational","new_status":"operational"},{"code":"ztxqdqqcnyvf","name":"Cloud NGFW for Azure - northeurope","old_status":"operational","new_status":"operational"},{"code":"6tj8rj12yj9n","name":"Cloud NGFW for Azure - uksouth","old_status":"operational","new_status":"operational"},{"code":"q7rr14g803x4","name":"Cloud NGFW for Azure - ukwest","old_status":"operational","new_status":"operational"},{"code":"rmn0j5t26164","name":"Cloud NGFW for Azure - westeurope","old_status":"operational","new_status":"degraded_performance"},{"code":"dzrklwwcvqwd","name":"Cloud NGFW for Azure - westus","old_status":"operational","new_status":"operational"},{"code":"pr7frkm0nn8t","name":"Cloud NGFW for Azure - westus2","old_status":"operational","new_status":"operational"},{"code":"c61v8wxxk3dl","name":"Cloud NGFW for Azure - westus3","old_status":"operational","new_status":"operational"},{"code":"q441ddyb08d9","name":"Cloud NGFW for Azure - brazilsouth","old_status":"operational","new_status":"operational"},{"code":"q9n3z9r6f5hl","name":"Cloud NGFW for Azure - japaneast","old_status":"operational","new_status":"operational"},{"code":"1thk09f83tvq","name":"Cloud NGFW for Azure - northcentralus","old_status":"operational","new_status":"operational"},{"code":"372t6yz2h09m","name":"Cloud NGFW for Azure - southeastasia","old_status":"operational","new_status":"operational"},{"code":"zlhd8f97zdvs","name":"Cloud NGFW for Azure - canadaeast","old_status":"operational","new_status":"operational"},{"code":"44566lqf64l8","name":"Cloud NGFW for Azure - centralindia","old_status":"operational","new_status":"operational"},{"code":"vn81g46sd4nl","name":"Cloud NGFW for Azure - francecentral","old_status":"operational","new_status":"operational"},{"code":"x30qbkw3r7kh","name":"Cloud NGFW for Azure - germanywestcentral","old_status":"operational","new_status":"operational"},{"code":"q036sjp6t782","name":"Cloud NGFW for Azure - israelcentral","old_status":"operational","new_status":"operational"},{"code":"z8vl0b0gfrz1","name":"Cloud NGFW for Azure - italynorth","old_status":"operational","new_status":"operational"},{"code":"6jxgr5d17zxc","name":"Cloud NGFW for Azure - japanwest","old_status":"operational","new_status":"operational"},{"code":"fkg7zyvtyhvd","name":"Cloud NGFW for Azure - koreacentral","old_status":"operational","new_status":"operational"},{"code":"wmj90v8ybf8m","name":"Cloud NGFW for Azure - mexicocentral","old_status":"operational","new_status":"operational"},{"code":"dnthqvt3my77","name":"Cloud NGFW for Azure - newzealandnorth","old_status":"operational","new_status":"operational"},{"code":"rvyv5pq8yt51","name":"Cloud NGFW for Azure - norwayeast","old_status":"operational","new_status":"operational"},{"code":"cm5mnq16ds14","name":"Cloud NGFW for Azure - southafricanorth","old_status":"operational","new_status":"operational"},{"code":"nzfz4y4t2609","name":"Cloud NGFW for Azure - southcentralus","old_status":"operational","new_status":"degraded_performance"},{"code":"k0rv77zfscyn","name":"Cloud NGFW for Azure - southindia","old_status":"operational","new_status":"operational"},{"code":"08kf4wrjm0gk","name":"Cloud NGFW for Azure - spaincentral","old_status":"operational","new_status":"operational"},{"code":"n8vn15tcm77m","name":"Cloud NGFW for Azure - swedencentral","old_status":"operational","new_status":"operational"},{"code":"xs6wzpqghs2z","name":"Cloud NGFW for Azure - switzerlandnorth","old_status":"operational","new_status":"operational"},{"code":"0mzg05k0g61y","name":"Cloud NGFW for Azure - switzerlandwest","old_status":"operational","new_status":"operational"},{"code":"9py5w1vt566g","name":"Cloud NGFW for Azure - uaenorth","old_status":"operational","new_status":"operational"},{"code":"mqlsh01qn7k4","name":"Cloud NGFW for Azure - westcentralus","old_status":"operational","new_status":"operational"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"v45fs6q744nt","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-07T18:06:04.984Z","_parsedEndTime":null},{"id":"3tx3nnmbwyh9","title":"Project status change failures in multiple regions","description":"Status: investigating\n\nWe are currently investigating an issue affecting project creation in multiple regions.","pubDate":"2026-07-10T18:41:44.959Z","link":"https://stspg.io/v2kqtvng9qnt","status":"monitoring","impact":"major","isResolved":false,"created_at":"2026-06-30T03:08:41.000Z","resolved_at":null,"started_at":"2026-06-30T03:08:41.000Z","startTime":"2026-06-30T03:08:41.000Z","endTime":null,"updatedAt":"2026-07-10T18:41:44.959Z","incidentUpdates":[],"affectedComponents":[{"id":"xcf1ntwt3n1p","name":"ap-northeast-1","status":"operational","created_at":"2025-01-10T16:56:23.753Z","updated_at":"2026-07-06T16:36:48.890Z","position":2,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"8wbvwkm1frpt","name":"ap-northeast-2","status":"operational","created_at":"2025-01-10T16:56:30.982Z","updated_at":"2026-07-06T16:36:48.908Z","position":3,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"prrc7382xy5j","name":"ap-south-1","status":"operational","created_at":"2025-01-10T16:56:37.612Z","updated_at":"2026-07-06T16:36:48.923Z","position":4,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"nsjdj4pzb9nr","name":"ap-southeast-1","status":"operational","created_at":"2025-01-10T16:52:01.851Z","updated_at":"2026-07-06T16:36:48.938Z","position":5,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"8lsy45ykh91b","name":"ap-southeast-2","status":"operational","created_at":"2025-01-10T16:56:44.004Z","updated_at":"2026-07-06T16:36:48.953Z","position":6,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"hf2cz18jnj92","name":"ca-central-1","status":"operational","created_at":"2025-01-10T16:57:16.979Z","updated_at":"2026-07-06T16:36:48.969Z","position":7,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"hzvb6v63k20m","name":"eu-central-1","status":"operational","created_at":"2025-01-10T16:57:29.169Z","updated_at":"2026-07-06T16:36:48.984Z","position":8,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"mzjn8lwgnb69","name":"eu-central-2","status":"operational","created_at":"2025-01-10T16:57:36.108Z","updated_at":"2026-07-06T16:36:49.000Z","position":9,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"xhpx25nnldh5","name":"eu-north-1","status":"operational","created_at":"2025-01-10T16:57:43.756Z","updated_at":"2026-07-06T16:36:49.015Z","position":10,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"0qtzyc40p8q9","name":"eu-west-1","status":"operational","created_at":"2025-01-10T16:54:57.835Z","updated_at":"2026-07-06T16:36:49.031Z","position":11,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"qpszx8dqhvwq","name":"eu-west-2","status":"operational","created_at":"2025-01-10T16:54:28.528Z","updated_at":"2026-07-06T16:36:49.045Z","position":12,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"mslb07nvjswt","name":"eu-west-3","status":"operational","created_at":"2025-01-10T16:53:53.671Z","updated_at":"2026-07-06T16:36:49.060Z","position":13,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"c1nccxytwfhx","name":"sa-east-1","status":"operational","created_at":"2025-01-10T16:57:51.563Z","updated_at":"2026-07-06T16:36:49.074Z","position":14,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"gx5p5zhkgl8f","name":"us-east-1","status":"operational","created_at":"2025-01-10T16:57:59.073Z","updated_at":"2026-07-06T16:36:49.089Z","position":15,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"1wd1zrc846g6","name":"us-east-2","status":"operational","created_at":"2025-01-10T16:58:15.807Z","updated_at":"2026-07-06T16:36:49.103Z","position":16,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"bcpt22h2w3pk","name":"us-west-1","status":"operational","created_at":"2025-01-10T16:58:22.218Z","updated_at":"2026-07-06T16:36:49.118Z","position":17,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false}],"guid":"3tx3nnmbwyh9","originalData":{"id":"3tx3nnmbwyh9","name":"Project status change failures in multiple regions","status":"monitoring","created_at":"2026-06-30T02:38:13.608Z","updated_at":"2026-07-10T18:41:44.959Z","monitoring_at":"2026-07-06T16:36:49.148Z","resolved_at":null,"impact":"major","shortlink":"https://stspg.io/v2kqtvng9qnt","started_at":"2026-06-30T03:08:41.000Z","page_id":"q7pxfmcf2sbx","incident_updates":"[Circular Reference]","components":"[Circular Reference]","reminder_intervals":null},"source":"api","vendor":"Supabase","healthScoreSeverity":"major","healthScoreSeveritySource":"impact","vendorId":"supabase","_parsedIsResolved":false,"_parsedStartTime":"2026-06-30T03:08:41.000Z","_parsedEndTime":null},{"id":"g8g0t84w1qdp","title":"Prisma Access : Prisma Access: New Customer onboarding failures","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Ashburn, The Dalles</p><p><strong>Impact:</strong></p><p>Prisma Access Engineering has identified new customer onboarding failure for below locations:</p><p>Australia South, Brazil Southeast, Canada Central, Canada East, Colombia Central, France North, France South East, India South Central, Israel Central, Japan Central, Japan South, Mexico Northeast, Saudi Arabia, Saudi Arabia West, South Korea, Sweden, Switzerland, UK, UK West, United Arab Emirates, US East, US Midwest, US West, US West Central.</p><br><p>Currently no workaround exists and teams are actively working on resolution.</p><p><strong>Workaround:</strong></p><p>NA</p><br><p>An incident has been identified. We are actively investigating to restore services.</p>","pubDate":"2026-06-08T17:30:21.530Z","link":"https://stspg.io/s7f5vq6x08b9","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-06-08T17:30:21.530Z","resolved_at":null,"startTime":"2026-06-08T17:30:21.530Z","endTime":null,"updatedAt":"2026-06-13T12:06:58.636Z","affectedComponents":["Configuration"],"incidentUpdates":[{"id":"b153tpymxygd","status":"monitoring","body":"<p><strong>Status:</strong> Monitoring</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Ashburn, The Dalles</p><p><strong>Impact:</strong></p><p>Prisma Access Engineering has identified new customer onboarding failure for below locations:</p><p>Australia South, Brazil Southeast, Canada Central, Canada East, Colombia Central, France North, France South East, India South Central, Israel Central, Japan Central, Japan South, Mexico Northeast, Saudi Arabia, Saudi Arabia West, South Korea, Sweden, Switzerland, UK, UK West, United Arab Emirates, US East, US Midwest, US West, US West Central.</p><br><p>Currently no workaround exists and teams are actively working on resolution.</p><p><strong>Workaround:</strong></p><p>NA</p><br><p>A fix has been implemented. We are actively monitoring to ensure full restoration of services.</p>","incident_id":"g8g0t84w1qdp","created_at":"2026-06-13T12:06:58.609Z","updated_at":"2026-06-13T12:06:58.609Z","display_at":"2026-06-13T12:06:58.609Z","affected_components":[{"code":"pzlzfsqd19dn","name":"Prisma Access - Configuration","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"2r9qs8199w8z","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Ashburn, The Dalles</p><p><strong>Impact:</strong></p><p>Prisma Access Engineering has identified new customer onboarding failure for below locations:</p><p>Australia South, Brazil Southeast, Canada Central, Canada East, Colombia Central, France North, France South East, India South Central, Israel Central, Japan Central, Japan South, Mexico Northeast, Saudi Arabia, Saudi Arabia West, South Korea, Sweden, Switzerland, UK, UK West, United Arab Emirates, US East, US Midwest, US West, US West Central.</p><br><p>Currently no workaround exists and teams are actively working on resolution.</p><p><strong>Workaround:</strong></p><p>NA</p><br><p>An incident has been identified. We are actively investigating to restore services.</p>","incident_id":"g8g0t84w1qdp","created_at":"2026-06-08T17:30:21.530Z","updated_at":"2026-06-08T17:30:21.530Z","display_at":"2026-06-08T17:30:21.530Z","affected_components":[{"code":"pzlzfsqd19dn","name":"Prisma Access - Configuration","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"g8g0t84w1qdp","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-06-08T17:30:21.530Z","_parsedEndTime":null},{"id":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>11:12</var> UTC</small><br><strong>Monitoring</strong> - Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.<br /><br />We apologise for the disruption and thank you for your patience.</p>","pubDate":"2026-05-08T11:12:09.000Z","link":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","status":"monitoring","impact":"none","isResolved":false,"created_at":"2026-05-08T11:12:09.000Z","resolved_at":null,"started_at":null,"startTime":"2026-05-08T11:12:09.000Z","endTime":null,"updatedAt":"2026-05-08T11:12:09.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","originalData":{"title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>11:12</var> UTC</small><br><strong>Monitoring</strong> - Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.<br /><br />We apologise for the disruption and thank you for your patience.</p>","pubDate":"Fri, 08 May 2026 11:12:09 +0000","link":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","guid":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://talent.status.atlassian.com/history.rss","firstSeen":"2026-05-08T11:14:01.074Z","lastUpdated":"2026-05-08T11:14:01.074Z","_productName":"Talent","source":"atlassian-rss"},"source":"api","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","vendorId":"atlassian","vendor":"Atlassian","_parsedIsResolved":false,"_parsedStartTime":"2026-05-08T11:12:09.000Z","_parsedEndTime":null},{"id":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>08:03</var> UTC</small><br><strong>Monitoring</strong> - We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.</p>","pubDate":"2026-05-08T08:03:04.000Z","link":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","status":"monitoring","impact":"none","isResolved":false,"created_at":"2026-05-08T08:03:04.000Z","resolved_at":null,"started_at":null,"startTime":"2026-05-08T08:03:04.000Z","endTime":null,"updatedAt":"2026-05-08T08:03:04.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","originalData":{"title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>08:03</var> UTC</small><br><strong>Monitoring</strong> - We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.</p>","pubDate":"Fri, 08 May 2026 08:03:04 +0000","link":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","guid":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://talent.status.atlassian.com/history.rss","firstSeen":"2026-05-08T10:14:01.204Z","lastUpdated":"2026-05-08T10:14:01.204Z","_productName":"Talent","source":"atlassian-rss"},"source":"api","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","vendorId":"atlassian","vendor":"Atlassian","_parsedIsResolved":false,"_parsedStartTime":"2026-05-08T08:03:04.000Z","_parsedEndTime":null},{"id":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","incidentId":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","title":"Atlassian Login Issues - Global Users","description":"<p><small>Apr <var data-var='date'>13</var>, <var data-var='time'>07:29</var> UTC</small><br><strong>Monitoring</strong> - Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact.<br /><br />Our team is investigating with urgency, and we will provide an update within 1 hour.</p>","pubDate":"Mon, 13 Apr 2026 07:29:45 +0000","link":"https://status.salesforce.com/incidents/https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","status":"unknown","impact":"minor","type":null,"isResolved":false,"created_at":"Mon, 13 Apr 2026 07:29:45 +0000","resolved_at":null,"startTime":"Mon, 13 Apr 2026 07:29:45 +0000","endTime":null,"updatedAt":"Mon, 13 Apr 2026 07:29:45 +0000","affectedComponents":[],"serviceKeys":[],"instanceKeys":[],"enhancedInstanceKeys":[],"incidentImpacts":[],"timeline":[],"guid":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","vendor":"Salesforce","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"salesforce","_parsedIsResolved":true,"_parsedStartTime":"2026-04-13T07:29:45.000Z","_parsedEndTime":null},{"title":"AWS Datacentres availability impacted due to power issues.","description":"<p> <small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:45</var> UTC</small><br> <strong>Identified</strong> - The issue has been identified and a fix is being implemented. </p> <p> <small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:42</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating this issue. </p>","pubDate":"Tue, 03 Mar 2026 16:45:13 +0000","link":"https://status.fortisiem.forticloud.com/incidents/0xltszgkcrm2","guid":"https://status.fortisiem.forticloud.com/incidents/0xltszgkcrm2","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.fortisiem.forticloud.com/history.rss","firstSeen":"2026-03-03T16:43:01.255Z","lastUpdated":"2026-05-22T08:03:00.892Z","vendor":"Fortinet","isResolved":false,"status":"unknown","startTime":"2026-03-03T16:42:00.000Z","started_at":"2026-03-03T16:42:00.000Z","resolved_at":null,"resolvedAt":null,"healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"fortinet","_parsedIsResolved":true,"_parsedStartTime":"2026-03-03T16:42:00.000Z","_parsedEndTime":null},{"id":"pgp51rgy1kqr","title":"AWS  Middle East(Bahrain) outage impacting Cloud NGFW Services.","description":"Status: monitoring\n\nAWS  Middle East(Bahrain) outage impacting Cloud NGFW Services.\nWe are aware of power outage in AWS Bahrain region. We are evaluating the impact on Cloud NGFW services in this region. Customers may experience failures to deploy new resources in this region.\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the AWS Status Page: https://health.aws.amazon.com/health/status?path=service-history\nNext Update: 5:00PM 3/03/2026 UTC.","pubDate":"2026-03-02T22:49:04.945Z","link":"https://stspg.io/psfg42ht97mh","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-03-02T22:49:04.945Z","resolved_at":null,"startTime":"2026-03-02T22:49:04.945Z","endTime":null,"updatedAt":"2026-04-02T18:07:08.590Z","affectedComponents":["Bahrain (me-south-1)"],"incidentUpdates":[{"id":"w15z9zgh2l8v","status":"monitoring","body":"We are continuing to monitor for any further issues.","incident_id":"pgp51rgy1kqr","created_at":"2026-04-02T18:05:13.531Z","updated_at":"2026-04-02T18:05:13.531Z","display_at":"2026-04-02T18:05:13.531Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain (me-south-1)","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":false,"custom_tweet":null,"tweet_id":null},{"id":"4hk1ntp0yr1j","status":"monitoring","body":"We are continuing to monitor for any further issues.","incident_id":"pgp51rgy1kqr","created_at":"2026-03-03T19:06:09.120Z","updated_at":"2026-03-03T19:06:09.120Z","display_at":"2026-03-03T19:06:09.120Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain(me-south-1)","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"grylw90jljpn","status":"monitoring","body":"We are continuing to monitor for any further issues.","incident_id":"pgp51rgy1kqr","created_at":"2026-03-03T03:10:57.034Z","updated_at":"2026-03-03T03:10:57.034Z","display_at":"2026-03-03T03:10:57.034Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain(me-south-1)","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"r6npwrwtnz60","status":"monitoring","body":"AWS  Middle East(Bahrain) outage impacting Cloud NGFW Services.\nWe are aware of power outage in AWS Bahrain region. We are evaluating the impact on Cloud NGFW services in this region. Customers may experience failures to deploy new resources in this region.\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the AWS Status Page: https://health.aws.amazon.com/health/status?path=service-history\nNext Update: 5:00PM 3/03/2026 UTC.","incident_id":"pgp51rgy1kqr","created_at":"2026-03-02T22:49:05.040Z","updated_at":"2026-03-03T13:00:39.298Z","display_at":"2026-03-02T22:49:05.000Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain(me-south-1)","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"pgp51rgy1kqr","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-03-02T22:49:04.945Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/a6b43a3d-15ca-4e4e-9c23-3c1e6d91cbfd","title":"Email Delivery Failure – System Outbound Block","description":"[Resolved] The issue has been mitigated and systems are now stable. We’ve marked this incident as resolved, but we will continue to monitor closely to ensure full recovery and prevent recurrence.","pubDate":"Wed, 01 Oct 2025 12:13:19 -0700","link":"https://status.lastpass.com/incidents/a6b43a3d-15ca-4e4e-9c23-3c1e6d91cbfd","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 01 Oct 2025 12:13:19 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 01 Oct 2025 12:13:19 -0700","endTime":null,"updatedAt":"Wed, 01 Oct 2025 12:13:19 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/a6b43a3d-15ca-4e4e-9c23-3c1e6d91cbfd","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2025-10-01T19:13:19.000Z","_parsedEndTime":null}],"remainingMonitoringCount":11,"remainingMonitoringIncidents":[{"title":"ZDX Copilot Experiencing Degraded Performance for Entity-Based Questions","link":"https://trust.zscaler.com/posts/30651","description":"<div class=\"update-list update-1\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 20:03:56 UTC</span></p><p>We have identified the root cause of the issue and working on resolution.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 21:20:35 UTC</span></p><p>e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.</p></div>","pubDate":"Sat, 11 Jul 2026 19:43:42 GMT","guid":"30651 at https://trust.zscaler.com","id":"30651","clouds":["zdxcloud.net"],"updates":[{"time":"Sat, 11 Jul 2026 20:03:56 UTC","update":"We have identified the root cause of the issue and working on resolution.","status":"In-Progress"},{"time":"Sat, 11 Jul 2026 21:20:35 UTC","update":"e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.","status":"In-Progress"}],"latest_update":[{"time":"Sat, 11 Jul 2026 21:20:35 UTC","update":"We have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.","status":"In-Progress"}],"root_cause":"","startTime":"Sat, 11 Jul 2026 18:00:00 GMT","endTime":null,"eventType":"Under Investigation","customerImpact":"Customers using ZDX Copilot may see degraded performance when asking questions that involve users, devices, applications and other entities.","availableWorkaround":"","nextUpdate":"12 Jul 2026 04:00 UTC","summary":"","category":{"name":"Recent incident","domain":"https://trust.zscaler.com"},"current_status":"In Progress","originalData":{"id":"30651","title":"ZDX Copilot Experiencing Degraded Performance for Entity-Based Questions","clouds":"[Circular Reference]","link":"https://trust.zscaler.com/posts/30651","description":"<div class=\"update-list update-1\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 20:03:56 UTC</span></p><p>We have identified the root cause of the issue and working on resolution.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sat, 11 Jul 2026 21:20:35 UTC</span></p><p>e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.</p></div>","updates":[{"time":"Sat, 11 Jul 2026 20:03:56 UTC","update":"We have identified the root cause of the issue and working on resolution.","status":"In-Progress"},{"time":"Sat, 11 Jul 2026 21:20:35 UTC","update":"e have identified the underlying backend issue affecting ZDX Copilot and are actively working to restore normal service. To accelerate recovery, we have prioritized restoration efforts for the most impacted customers and begun reloading key data sets across affected environments. We are also working closely with vendor on backend capacity improvements to support full service restoration. We will continue to share updates as progress is made.","status":"In-Progress"}],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Sat, 11 Jul 2026 19:43:42 GMT","resolved_date":null,"startTime":"Sat, 11 Jul 2026 18:00:00 GMT","endTime":"","eventType":"Under Investigation","customerImpact":"Customers using ZDX Copilot may see degraded performance when asking questions that involve users, devices, applications and other entities.","availableWorkaround":"","nextUpdate":"12 Jul 2026 04:00 UTC","summary":"","category":"[Circular Reference]","current_status":"In Progress"},"feedUrl":"https://trust.zscaler.com/rss-feed/incidents?_format=json","trustEnvironment":"Commercial","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-07-11T20:02:00.246Z","lastUpdated":"2026-07-11T21:22:01.192Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-07-11T18:00:00.000Z","_parsedEndTime":null},{"id":"https://status.bigid.com/incidents/7n76jb4x1czb","title":"07-10-2026 Incident","description":"<p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>18:10</var> UTC</small><br> <strong>Monitoring</strong> - A fix has been implemented, and we are monitoring the results.<br /><br />We will provide the next update by 04:00 UTC. </p> <p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>17:39</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating performance degradation affecting one of our clusters.<br /><br />Our team is actively looking into the issue and will provide the next update by 20:00 UTC. </p>","pubDate":"2026-07-10T18:10:02.000Z","link":"https://status.bigid.com/incidents/7n76jb4x1czb","status":"monitoring","impact":"none","isResolved":false,"created_at":"2026-07-10T17:39:00.000Z","resolved_at":null,"started_at":"2026-07-10T17:39:00.000Z","startTime":"2026-07-10T17:39:00.000Z","endTime":null,"updatedAt":"2026-07-10T18:10:02.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.bigid.com/incidents/7n76jb4x1czb","originalData":{"title":"07-10-2026 Incident","description":"<p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>18:10</var> UTC</small><br> <strong>Monitoring</strong> - A fix has been implemented, and we are monitoring the results.<br /><br />We will provide the next update by 04:00 UTC. </p> <p> <small>Jul <var data-var='date'>10</var>, <var data-var='time'>17:39</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating performance degradation affecting one of our clusters.<br /><br />Our team is actively looking into the issue and will provide the next update by 20:00 UTC. </p>","pubDate":"Fri, 10 Jul 2026 18:10:02 +0000","link":"https://status.bigid.com/incidents/7n76jb4x1czb","guid":"https://status.bigid.com/incidents/7n76jb4x1czb","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.bigid.com/history.rss","firstSeen":"2026-07-10T17:44:00.720Z","lastUpdated":"2026-07-10T18:14:00.461Z","vendor":"BigID","source":"rss-feed"},"source":"rss-feed","vendor":"BigID","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"bigid","_parsedIsResolved":false,"_parsedStartTime":"2026-07-10T17:39:00.000Z","_parsedEndTime":null},{"id":"v45fs6q744nt","title":"Azure westeurope, southcentralus outage impacting Cloud NGFW Services.","description":"Status: monitoring\n\nWe have identified an issue with Azure affecting the Cloud NGFW westeurope and southcentralus regions. Customers may experience failures to during autoscaling and during deployment of new resources.\n\nCurrent Status: Azure is currently experiencing compute capacity issues within the regions. This is impacting our ability to scale out new virtual machines. \n\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. \n\nNext Update: Fri, July  11th, 01:00UTC","pubDate":"2026-07-07T18:06:04.984Z","link":"https://stspg.io/zfhnnrf4ksg7","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-07-07T18:06:04.984Z","resolved_at":null,"startTime":"2026-07-07T18:06:04.984Z","endTime":null,"updatedAt":"2026-07-10T09:21:36.435Z","affectedComponents":["australiaeast","australiasoutheast","canadacentral","centralus","eastasia","eastus","eastus2","northeurope","uksouth","ukwest","westeurope","westus","westus2","westus3","brazilsouth","japaneast","northcentralus","southeastasia","canadaeast","centralindia","francecentral","germanywestcentral","israelcentral","italynorth","japanwest","koreacentral","mexicocentral","newzealandnorth","norwayeast","southafricanorth","southcentralus","southindia","spaincentral","swedencentral","switzerlandnorth","switzerlandwest","uaenorth","westcentralus"],"incidentUpdates":[{"id":"7zckmylydfcs","status":"monitoring","body":"Azure is still working on recovery. We are continuously monitoring their progress.","incident_id":"v45fs6q744nt","created_at":"2026-07-10T09:16:24.296Z","updated_at":"2026-07-10T09:16:24.296Z","display_at":"2026-07-10T09:16:24.296Z","affected_components":[{"code":"nj5xnr1lyh1g","name":"Cloud NGFW for Azure - australiaeast","old_status":"operational","new_status":"operational"},{"code":"29jkdyh9zyqf","name":"Cloud NGFW for Azure - australiasoutheast","old_status":"operational","new_status":"operational"},{"code":"c179jwk1czjd","name":"Cloud NGFW for Azure - canadacentral","old_status":"operational","new_status":"operational"},{"code":"xpryk8b9yxdh","name":"Cloud NGFW for Azure - centralus","old_status":"operational","new_status":"operational"},{"code":"twl8v5dtbwq5","name":"Cloud NGFW for Azure - eastasia","old_status":"operational","new_status":"operational"},{"code":"nwh2fyy9xdf1","name":"Cloud NGFW for Azure - eastus","old_status":"operational","new_status":"operational"},{"code":"hbdk3yc4g006","name":"Cloud NGFW for Azure - eastus2","old_status":"operational","new_status":"operational"},{"code":"ztxqdqqcnyvf","name":"Cloud NGFW for Azure - northeurope","old_status":"operational","new_status":"operational"},{"code":"6tj8rj12yj9n","name":"Cloud NGFW for Azure - uksouth","old_status":"operational","new_status":"operational"},{"code":"q7rr14g803x4","name":"Cloud NGFW for Azure - ukwest","old_status":"operational","new_status":"operational"},{"code":"rmn0j5t26164","name":"Cloud NGFW for Azure - westeurope","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"dzrklwwcvqwd","name":"Cloud NGFW for Azure - westus","old_status":"operational","new_status":"operational"},{"code":"pr7frkm0nn8t","name":"Cloud NGFW for Azure - westus2","old_status":"operational","new_status":"operational"},{"code":"c61v8wxxk3dl","name":"Cloud NGFW for Azure - westus3","old_status":"operational","new_status":"operational"},{"code":"q441ddyb08d9","name":"Cloud NGFW for Azure - brazilsouth","old_status":"operational","new_status":"operational"},{"code":"q9n3z9r6f5hl","name":"Cloud NGFW for Azure - japaneast","old_status":"operational","new_status":"operational"},{"code":"1thk09f83tvq","name":"Cloud NGFW for Azure - northcentralus","old_status":"operational","new_status":"operational"},{"code":"372t6yz2h09m","name":"Cloud NGFW for Azure - southeastasia","old_status":"operational","new_status":"operational"},{"code":"zlhd8f97zdvs","name":"Cloud NGFW for Azure - canadaeast","old_status":"operational","new_status":"operational"},{"code":"44566lqf64l8","name":"Cloud NGFW for Azure - centralindia","old_status":"operational","new_status":"operational"},{"code":"vn81g46sd4nl","name":"Cloud NGFW for Azure - francecentral","old_status":"operational","new_status":"operational"},{"code":"x30qbkw3r7kh","name":"Cloud NGFW for Azure - germanywestcentral","old_status":"operational","new_status":"operational"},{"code":"q036sjp6t782","name":"Cloud NGFW for Azure - israelcentral","old_status":"operational","new_status":"operational"},{"code":"z8vl0b0gfrz1","name":"Cloud NGFW for Azure - italynorth","old_status":"operational","new_status":"operational"},{"code":"6jxgr5d17zxc","name":"Cloud NGFW for Azure - japanwest","old_status":"operational","new_status":"operational"},{"code":"fkg7zyvtyhvd","name":"Cloud NGFW for Azure - koreacentral","old_status":"operational","new_status":"operational"},{"code":"wmj90v8ybf8m","name":"Cloud NGFW for Azure - mexicocentral","old_status":"operational","new_status":"operational"},{"code":"dnthqvt3my77","name":"Cloud NGFW for Azure - newzealandnorth","old_status":"operational","new_status":"operational"},{"code":"rvyv5pq8yt51","name":"Cloud NGFW for Azure - norwayeast","old_status":"operational","new_status":"operational"},{"code":"cm5mnq16ds14","name":"Cloud NGFW for Azure - southafricanorth","old_status":"operational","new_status":"operational"},{"code":"nzfz4y4t2609","name":"Cloud NGFW for Azure - southcentralus","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"k0rv77zfscyn","name":"Cloud NGFW for Azure - southindia","old_status":"operational","new_status":"operational"},{"code":"08kf4wrjm0gk","name":"Cloud NGFW for Azure - spaincentral","old_status":"operational","new_status":"operational"},{"code":"n8vn15tcm77m","name":"Cloud NGFW for Azure - swedencentral","old_status":"operational","new_status":"operational"},{"code":"xs6wzpqghs2z","name":"Cloud NGFW for Azure - switzerlandnorth","old_status":"operational","new_status":"operational"},{"code":"0mzg05k0g61y","name":"Cloud NGFW for Azure - switzerlandwest","old_status":"operational","new_status":"operational"},{"code":"9py5w1vt566g","name":"Cloud NGFW for Azure - uaenorth","old_status":"operational","new_status":"operational"},{"code":"mqlsh01qn7k4","name":"Cloud NGFW for Azure - westcentralus","old_status":"operational","new_status":"operational"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"7whh642m1d4t","status":"monitoring","body":"Azure is still working on recovery. We are continuously monitoring their progress.","incident_id":"v45fs6q744nt","created_at":"2026-07-08T15:45:37.737Z","updated_at":"2026-07-08T15:45:37.737Z","display_at":"2026-07-08T15:45:37.737Z","affected_components":[{"code":"nj5xnr1lyh1g","name":"Cloud NGFW for Azure - australiaeast","old_status":"operational","new_status":"operational"},{"code":"29jkdyh9zyqf","name":"Cloud NGFW for Azure - australiasoutheast","old_status":"operational","new_status":"operational"},{"code":"c179jwk1czjd","name":"Cloud NGFW for Azure - canadacentral","old_status":"operational","new_status":"operational"},{"code":"xpryk8b9yxdh","name":"Cloud NGFW for Azure - centralus","old_status":"operational","new_status":"operational"},{"code":"twl8v5dtbwq5","name":"Cloud NGFW for Azure - eastasia","old_status":"operational","new_status":"operational"},{"code":"nwh2fyy9xdf1","name":"Cloud NGFW for Azure - eastus","old_status":"operational","new_status":"operational"},{"code":"hbdk3yc4g006","name":"Cloud NGFW for Azure - eastus2","old_status":"operational","new_status":"operational"},{"code":"ztxqdqqcnyvf","name":"Cloud NGFW for Azure - northeurope","old_status":"operational","new_status":"operational"},{"code":"6tj8rj12yj9n","name":"Cloud NGFW for Azure - uksouth","old_status":"operational","new_status":"operational"},{"code":"q7rr14g803x4","name":"Cloud NGFW for Azure - ukwest","old_status":"operational","new_status":"operational"},{"code":"rmn0j5t26164","name":"Cloud NGFW for Azure - westeurope","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"dzrklwwcvqwd","name":"Cloud NGFW for Azure - westus","old_status":"operational","new_status":"operational"},{"code":"pr7frkm0nn8t","name":"Cloud NGFW for Azure - westus2","old_status":"operational","new_status":"operational"},{"code":"c61v8wxxk3dl","name":"Cloud NGFW for Azure - westus3","old_status":"operational","new_status":"operational"},{"code":"q441ddyb08d9","name":"Cloud NGFW for Azure - brazilsouth","old_status":"operational","new_status":"operational"},{"code":"q9n3z9r6f5hl","name":"Cloud NGFW for Azure - japaneast","old_status":"operational","new_status":"operational"},{"code":"1thk09f83tvq","name":"Cloud NGFW for Azure - northcentralus","old_status":"operational","new_status":"operational"},{"code":"372t6yz2h09m","name":"Cloud NGFW for Azure - southeastasia","old_status":"operational","new_status":"operational"},{"code":"zlhd8f97zdvs","name":"Cloud NGFW for Azure - canadaeast","old_status":"operational","new_status":"operational"},{"code":"44566lqf64l8","name":"Cloud NGFW for Azure - centralindia","old_status":"operational","new_status":"operational"},{"code":"vn81g46sd4nl","name":"Cloud NGFW for Azure - francecentral","old_status":"operational","new_status":"operational"},{"code":"x30qbkw3r7kh","name":"Cloud NGFW for Azure - germanywestcentral","old_status":"operational","new_status":"operational"},{"code":"q036sjp6t782","name":"Cloud NGFW for Azure - israelcentral","old_status":"operational","new_status":"operational"},{"code":"z8vl0b0gfrz1","name":"Cloud NGFW for Azure - italynorth","old_status":"operational","new_status":"operational"},{"code":"6jxgr5d17zxc","name":"Cloud NGFW for Azure - japanwest","old_status":"operational","new_status":"operational"},{"code":"fkg7zyvtyhvd","name":"Cloud NGFW for Azure - koreacentral","old_status":"operational","new_status":"operational"},{"code":"wmj90v8ybf8m","name":"Cloud NGFW for Azure - mexicocentral","old_status":"operational","new_status":"operational"},{"code":"dnthqvt3my77","name":"Cloud NGFW for Azure - newzealandnorth","old_status":"operational","new_status":"operational"},{"code":"rvyv5pq8yt51","name":"Cloud NGFW for Azure - norwayeast","old_status":"operational","new_status":"operational"},{"code":"cm5mnq16ds14","name":"Cloud NGFW for Azure - southafricanorth","old_status":"operational","new_status":"operational"},{"code":"nzfz4y4t2609","name":"Cloud NGFW for Azure - southcentralus","old_status":"degraded_performance","new_status":"degraded_performance"},{"code":"k0rv77zfscyn","name":"Cloud NGFW for Azure - southindia","old_status":"operational","new_status":"operational"},{"code":"08kf4wrjm0gk","name":"Cloud NGFW for Azure - spaincentral","old_status":"operational","new_status":"operational"},{"code":"n8vn15tcm77m","name":"Cloud NGFW for Azure - swedencentral","old_status":"operational","new_status":"operational"},{"code":"xs6wzpqghs2z","name":"Cloud NGFW for Azure - switzerlandnorth","old_status":"operational","new_status":"operational"},{"code":"0mzg05k0g61y","name":"Cloud NGFW for Azure - switzerlandwest","old_status":"operational","new_status":"operational"},{"code":"9py5w1vt566g","name":"Cloud NGFW for Azure - uaenorth","old_status":"operational","new_status":"operational"},{"code":"mqlsh01qn7k4","name":"Cloud NGFW for Azure - westcentralus","old_status":"operational","new_status":"operational"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"xqdwjrrpcts7","status":"monitoring","body":"We have identified an issue with Azure affecting the Cloud NGFW westeurope and southcentralus regions. Customers may experience failures to during autoscaling and during deployment of new resources.\n\nCurrent Status: Azure is currently experiencing compute capacity issues within the regions. This is impacting our ability to scale out new virtual machines. \n\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. \n\nNext Update: Fri, July  11th, 01:00UTC","incident_id":"v45fs6q744nt","created_at":"2026-07-07T18:06:05.160Z","updated_at":"2026-07-10T09:21:36.412Z","display_at":"2026-07-07T18:06:05.000Z","affected_components":[{"code":"nj5xnr1lyh1g","name":"Cloud NGFW for Azure - australiaeast","old_status":"operational","new_status":"operational"},{"code":"29jkdyh9zyqf","name":"Cloud NGFW for Azure - australiasoutheast","old_status":"operational","new_status":"operational"},{"code":"c179jwk1czjd","name":"Cloud NGFW for Azure - canadacentral","old_status":"operational","new_status":"operational"},{"code":"xpryk8b9yxdh","name":"Cloud NGFW for Azure - centralus","old_status":"operational","new_status":"operational"},{"code":"twl8v5dtbwq5","name":"Cloud NGFW for Azure - eastasia","old_status":"operational","new_status":"operational"},{"code":"nwh2fyy9xdf1","name":"Cloud NGFW for Azure - eastus","old_status":"operational","new_status":"operational"},{"code":"hbdk3yc4g006","name":"Cloud NGFW for Azure - eastus2","old_status":"operational","new_status":"operational"},{"code":"ztxqdqqcnyvf","name":"Cloud NGFW for Azure - northeurope","old_status":"operational","new_status":"operational"},{"code":"6tj8rj12yj9n","name":"Cloud NGFW for Azure - uksouth","old_status":"operational","new_status":"operational"},{"code":"q7rr14g803x4","name":"Cloud NGFW for Azure - ukwest","old_status":"operational","new_status":"operational"},{"code":"rmn0j5t26164","name":"Cloud NGFW for Azure - westeurope","old_status":"operational","new_status":"degraded_performance"},{"code":"dzrklwwcvqwd","name":"Cloud NGFW for Azure - westus","old_status":"operational","new_status":"operational"},{"code":"pr7frkm0nn8t","name":"Cloud NGFW for Azure - westus2","old_status":"operational","new_status":"operational"},{"code":"c61v8wxxk3dl","name":"Cloud NGFW for Azure - westus3","old_status":"operational","new_status":"operational"},{"code":"q441ddyb08d9","name":"Cloud NGFW for Azure - brazilsouth","old_status":"operational","new_status":"operational"},{"code":"q9n3z9r6f5hl","name":"Cloud NGFW for Azure - japaneast","old_status":"operational","new_status":"operational"},{"code":"1thk09f83tvq","name":"Cloud NGFW for Azure - northcentralus","old_status":"operational","new_status":"operational"},{"code":"372t6yz2h09m","name":"Cloud NGFW for Azure - southeastasia","old_status":"operational","new_status":"operational"},{"code":"zlhd8f97zdvs","name":"Cloud NGFW for Azure - canadaeast","old_status":"operational","new_status":"operational"},{"code":"44566lqf64l8","name":"Cloud NGFW for Azure - centralindia","old_status":"operational","new_status":"operational"},{"code":"vn81g46sd4nl","name":"Cloud NGFW for Azure - francecentral","old_status":"operational","new_status":"operational"},{"code":"x30qbkw3r7kh","name":"Cloud NGFW for Azure - germanywestcentral","old_status":"operational","new_status":"operational"},{"code":"q036sjp6t782","name":"Cloud NGFW for Azure - israelcentral","old_status":"operational","new_status":"operational"},{"code":"z8vl0b0gfrz1","name":"Cloud NGFW for Azure - italynorth","old_status":"operational","new_status":"operational"},{"code":"6jxgr5d17zxc","name":"Cloud NGFW for Azure - japanwest","old_status":"operational","new_status":"operational"},{"code":"fkg7zyvtyhvd","name":"Cloud NGFW for Azure - koreacentral","old_status":"operational","new_status":"operational"},{"code":"wmj90v8ybf8m","name":"Cloud NGFW for Azure - mexicocentral","old_status":"operational","new_status":"operational"},{"code":"dnthqvt3my77","name":"Cloud NGFW for Azure - newzealandnorth","old_status":"operational","new_status":"operational"},{"code":"rvyv5pq8yt51","name":"Cloud NGFW for Azure - norwayeast","old_status":"operational","new_status":"operational"},{"code":"cm5mnq16ds14","name":"Cloud NGFW for Azure - southafricanorth","old_status":"operational","new_status":"operational"},{"code":"nzfz4y4t2609","name":"Cloud NGFW for Azure - southcentralus","old_status":"operational","new_status":"degraded_performance"},{"code":"k0rv77zfscyn","name":"Cloud NGFW for Azure - southindia","old_status":"operational","new_status":"operational"},{"code":"08kf4wrjm0gk","name":"Cloud NGFW for Azure - spaincentral","old_status":"operational","new_status":"operational"},{"code":"n8vn15tcm77m","name":"Cloud NGFW for Azure - swedencentral","old_status":"operational","new_status":"operational"},{"code":"xs6wzpqghs2z","name":"Cloud NGFW for Azure - switzerlandnorth","old_status":"operational","new_status":"operational"},{"code":"0mzg05k0g61y","name":"Cloud NGFW for Azure - switzerlandwest","old_status":"operational","new_status":"operational"},{"code":"9py5w1vt566g","name":"Cloud NGFW for Azure - uaenorth","old_status":"operational","new_status":"operational"},{"code":"mqlsh01qn7k4","name":"Cloud NGFW for Azure - westcentralus","old_status":"operational","new_status":"operational"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"v45fs6q744nt","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-07T18:06:04.984Z","_parsedEndTime":null},{"id":"3tx3nnmbwyh9","title":"Project status change failures in multiple regions","description":"Status: investigating\n\nWe are currently investigating an issue affecting project creation in multiple regions.","pubDate":"2026-07-10T18:41:44.959Z","link":"https://stspg.io/v2kqtvng9qnt","status":"monitoring","impact":"major","isResolved":false,"created_at":"2026-06-30T03:08:41.000Z","resolved_at":null,"started_at":"2026-06-30T03:08:41.000Z","startTime":"2026-06-30T03:08:41.000Z","endTime":null,"updatedAt":"2026-07-10T18:41:44.959Z","incidentUpdates":[],"affectedComponents":[{"id":"xcf1ntwt3n1p","name":"ap-northeast-1","status":"operational","created_at":"2025-01-10T16:56:23.753Z","updated_at":"2026-07-06T16:36:48.890Z","position":2,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"8wbvwkm1frpt","name":"ap-northeast-2","status":"operational","created_at":"2025-01-10T16:56:30.982Z","updated_at":"2026-07-06T16:36:48.908Z","position":3,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"prrc7382xy5j","name":"ap-south-1","status":"operational","created_at":"2025-01-10T16:56:37.612Z","updated_at":"2026-07-06T16:36:48.923Z","position":4,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"nsjdj4pzb9nr","name":"ap-southeast-1","status":"operational","created_at":"2025-01-10T16:52:01.851Z","updated_at":"2026-07-06T16:36:48.938Z","position":5,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"8lsy45ykh91b","name":"ap-southeast-2","status":"operational","created_at":"2025-01-10T16:56:44.004Z","updated_at":"2026-07-06T16:36:48.953Z","position":6,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"hf2cz18jnj92","name":"ca-central-1","status":"operational","created_at":"2025-01-10T16:57:16.979Z","updated_at":"2026-07-06T16:36:48.969Z","position":7,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"hzvb6v63k20m","name":"eu-central-1","status":"operational","created_at":"2025-01-10T16:57:29.169Z","updated_at":"2026-07-06T16:36:48.984Z","position":8,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"mzjn8lwgnb69","name":"eu-central-2","status":"operational","created_at":"2025-01-10T16:57:36.108Z","updated_at":"2026-07-06T16:36:49.000Z","position":9,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"xhpx25nnldh5","name":"eu-north-1","status":"operational","created_at":"2025-01-10T16:57:43.756Z","updated_at":"2026-07-06T16:36:49.015Z","position":10,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"0qtzyc40p8q9","name":"eu-west-1","status":"operational","created_at":"2025-01-10T16:54:57.835Z","updated_at":"2026-07-06T16:36:49.031Z","position":11,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"qpszx8dqhvwq","name":"eu-west-2","status":"operational","created_at":"2025-01-10T16:54:28.528Z","updated_at":"2026-07-06T16:36:49.045Z","position":12,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"mslb07nvjswt","name":"eu-west-3","status":"operational","created_at":"2025-01-10T16:53:53.671Z","updated_at":"2026-07-06T16:36:49.060Z","position":13,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"c1nccxytwfhx","name":"sa-east-1","status":"operational","created_at":"2025-01-10T16:57:51.563Z","updated_at":"2026-07-06T16:36:49.074Z","position":14,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"gx5p5zhkgl8f","name":"us-east-1","status":"operational","created_at":"2025-01-10T16:57:59.073Z","updated_at":"2026-07-06T16:36:49.089Z","position":15,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"1wd1zrc846g6","name":"us-east-2","status":"operational","created_at":"2025-01-10T16:58:15.807Z","updated_at":"2026-07-06T16:36:49.103Z","position":16,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false},{"id":"bcpt22h2w3pk","name":"us-west-1","status":"operational","created_at":"2025-01-10T16:58:22.218Z","updated_at":"2026-07-06T16:36:49.118Z","position":17,"description":null,"showcase":false,"start_date":"2025-01-10","group_id":"36n3k66s7n2v","page_id":"q7pxfmcf2sbx","group":false,"only_show_if_degraded":false}],"guid":"3tx3nnmbwyh9","originalData":{"id":"3tx3nnmbwyh9","name":"Project status change failures in multiple regions","status":"monitoring","created_at":"2026-06-30T02:38:13.608Z","updated_at":"2026-07-10T18:41:44.959Z","monitoring_at":"2026-07-06T16:36:49.148Z","resolved_at":null,"impact":"major","shortlink":"https://stspg.io/v2kqtvng9qnt","started_at":"2026-06-30T03:08:41.000Z","page_id":"q7pxfmcf2sbx","incident_updates":"[Circular Reference]","components":"[Circular Reference]","reminder_intervals":null},"source":"api","vendor":"Supabase","healthScoreSeverity":"major","healthScoreSeveritySource":"impact","vendorId":"supabase","_parsedIsResolved":false,"_parsedStartTime":"2026-06-30T03:08:41.000Z","_parsedEndTime":null},{"id":"g8g0t84w1qdp","title":"Prisma Access : Prisma Access: New Customer onboarding failures","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Ashburn, The Dalles</p><p><strong>Impact:</strong></p><p>Prisma Access Engineering has identified new customer onboarding failure for below locations:</p><p>Australia South, Brazil Southeast, Canada Central, Canada East, Colombia Central, France North, France South East, India South Central, Israel Central, Japan Central, Japan South, Mexico Northeast, Saudi Arabia, Saudi Arabia West, South Korea, Sweden, Switzerland, UK, UK West, United Arab Emirates, US East, US Midwest, US West, US West Central.</p><br><p>Currently no workaround exists and teams are actively working on resolution.</p><p><strong>Workaround:</strong></p><p>NA</p><br><p>An incident has been identified. We are actively investigating to restore services.</p>","pubDate":"2026-06-08T17:30:21.530Z","link":"https://stspg.io/s7f5vq6x08b9","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-06-08T17:30:21.530Z","resolved_at":null,"startTime":"2026-06-08T17:30:21.530Z","endTime":null,"updatedAt":"2026-06-13T12:06:58.636Z","affectedComponents":["Configuration"],"incidentUpdates":[{"id":"b153tpymxygd","status":"monitoring","body":"<p><strong>Status:</strong> Monitoring</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Ashburn, The Dalles</p><p><strong>Impact:</strong></p><p>Prisma Access Engineering has identified new customer onboarding failure for below locations:</p><p>Australia South, Brazil Southeast, Canada Central, Canada East, Colombia Central, France North, France South East, India South Central, Israel Central, Japan Central, Japan South, Mexico Northeast, Saudi Arabia, Saudi Arabia West, South Korea, Sweden, Switzerland, UK, UK West, United Arab Emirates, US East, US Midwest, US West, US West Central.</p><br><p>Currently no workaround exists and teams are actively working on resolution.</p><p><strong>Workaround:</strong></p><p>NA</p><br><p>A fix has been implemented. We are actively monitoring to ensure full restoration of services.</p>","incident_id":"g8g0t84w1qdp","created_at":"2026-06-13T12:06:58.609Z","updated_at":"2026-06-13T12:06:58.609Z","display_at":"2026-06-13T12:06:58.609Z","affected_components":[{"code":"pzlzfsqd19dn","name":"Prisma Access - Configuration","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"2r9qs8199w8z","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Ashburn, The Dalles</p><p><strong>Impact:</strong></p><p>Prisma Access Engineering has identified new customer onboarding failure for below locations:</p><p>Australia South, Brazil Southeast, Canada Central, Canada East, Colombia Central, France North, France South East, India South Central, Israel Central, Japan Central, Japan South, Mexico Northeast, Saudi Arabia, Saudi Arabia West, South Korea, Sweden, Switzerland, UK, UK West, United Arab Emirates, US East, US Midwest, US West, US West Central.</p><br><p>Currently no workaround exists and teams are actively working on resolution.</p><p><strong>Workaround:</strong></p><p>NA</p><br><p>An incident has been identified. We are actively investigating to restore services.</p>","incident_id":"g8g0t84w1qdp","created_at":"2026-06-08T17:30:21.530Z","updated_at":"2026-06-08T17:30:21.530Z","display_at":"2026-06-08T17:30:21.530Z","affected_components":[{"code":"pzlzfsqd19dn","name":"Prisma Access - Configuration","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"g8g0t84w1qdp","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-06-08T17:30:21.530Z","_parsedEndTime":null},{"id":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>11:12</var> UTC</small><br><strong>Monitoring</strong> - Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.<br /><br />We apologise for the disruption and thank you for your patience.</p>","pubDate":"2026-05-08T11:12:09.000Z","link":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","status":"monitoring","impact":"none","isResolved":false,"created_at":"2026-05-08T11:12:09.000Z","resolved_at":null,"started_at":null,"startTime":"2026-05-08T11:12:09.000Z","endTime":null,"updatedAt":"2026-05-08T11:12:09.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","originalData":{"title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>11:12</var> UTC</small><br><strong>Monitoring</strong> - Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.<br /><br />We apologise for the disruption and thank you for your patience.</p>","pubDate":"Fri, 08 May 2026 11:12:09 +0000","link":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","guid":"https://talent.status.atlassian.com/incidents/h76cmy76g4rn","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://talent.status.atlassian.com/history.rss","firstSeen":"2026-05-08T11:14:01.074Z","lastUpdated":"2026-05-08T11:14:01.074Z","_productName":"Talent","source":"atlassian-rss"},"source":"api","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","vendorId":"atlassian","vendor":"Atlassian","_parsedIsResolved":false,"_parsedStartTime":"2026-05-08T11:12:09.000Z","_parsedEndTime":null},{"id":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>08:03</var> UTC</small><br><strong>Monitoring</strong> - We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.</p>","pubDate":"2026-05-08T08:03:04.000Z","link":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","status":"monitoring","impact":"none","isResolved":false,"created_at":"2026-05-08T08:03:04.000Z","resolved_at":null,"started_at":null,"startTime":"2026-05-08T08:03:04.000Z","endTime":null,"updatedAt":"2026-05-08T08:03:04.000Z","incidentUpdates":[],"affectedComponents":[],"guid":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","originalData":{"title":"Multiple Atlassian services are experiencing issues","description":"<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>08:03</var> UTC</small><br><strong>Monitoring</strong> - We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.</p>","pubDate":"Fri, 08 May 2026 08:03:04 +0000","link":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","guid":"https://talent.status.atlassian.com/incidents/wwtcqj5wycft","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://talent.status.atlassian.com/history.rss","firstSeen":"2026-05-08T10:14:01.204Z","lastUpdated":"2026-05-08T10:14:01.204Z","_productName":"Talent","source":"atlassian-rss"},"source":"api","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","vendorId":"atlassian","vendor":"Atlassian","_parsedIsResolved":false,"_parsedStartTime":"2026-05-08T08:03:04.000Z","_parsedEndTime":null},{"id":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","incidentId":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","title":"Atlassian Login Issues - Global Users","description":"<p><small>Apr <var data-var='date'>13</var>, <var data-var='time'>07:29</var> UTC</small><br><strong>Monitoring</strong> - Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact.<br /><br />Our team is investigating with urgency, and we will provide an update within 1 hour.</p>","pubDate":"Mon, 13 Apr 2026 07:29:45 +0000","link":"https://status.salesforce.com/incidents/https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","status":"unknown","impact":"minor","type":null,"isResolved":false,"created_at":"Mon, 13 Apr 2026 07:29:45 +0000","resolved_at":null,"startTime":"Mon, 13 Apr 2026 07:29:45 +0000","endTime":null,"updatedAt":"Mon, 13 Apr 2026 07:29:45 +0000","affectedComponents":[],"serviceKeys":[],"instanceKeys":[],"enhancedInstanceKeys":[],"incidentImpacts":[],"timeline":[],"guid":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","vendor":"Salesforce","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"salesforce","_parsedIsResolved":true,"_parsedStartTime":"2026-04-13T07:29:45.000Z","_parsedEndTime":null},{"title":"AWS Datacentres availability impacted due to power issues.","description":"<p> <small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:45</var> UTC</small><br> <strong>Identified</strong> - The issue has been identified and a fix is being implemented. </p> <p> <small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:42</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating this issue. </p>","pubDate":"Tue, 03 Mar 2026 16:45:13 +0000","link":"https://status.fortisiem.forticloud.com/incidents/0xltszgkcrm2","guid":"https://status.fortisiem.forticloud.com/incidents/0xltszgkcrm2","feedType":"feed","feedCategory":"rss","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.fortisiem.forticloud.com/history.rss","firstSeen":"2026-03-03T16:43:01.255Z","lastUpdated":"2026-05-22T08:03:00.892Z","vendor":"Fortinet","isResolved":false,"status":"unknown","startTime":"2026-03-03T16:42:00.000Z","started_at":"2026-03-03T16:42:00.000Z","resolved_at":null,"resolvedAt":null,"healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"fortinet","_parsedIsResolved":true,"_parsedStartTime":"2026-03-03T16:42:00.000Z","_parsedEndTime":null},{"id":"pgp51rgy1kqr","title":"AWS  Middle East(Bahrain) outage impacting Cloud NGFW Services.","description":"Status: monitoring\n\nAWS  Middle East(Bahrain) outage impacting Cloud NGFW Services.\nWe are aware of power outage in AWS Bahrain region. We are evaluating the impact on Cloud NGFW services in this region. Customers may experience failures to deploy new resources in this region.\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the AWS Status Page: https://health.aws.amazon.com/health/status?path=service-history\nNext Update: 5:00PM 3/03/2026 UTC.","pubDate":"2026-03-02T22:49:04.945Z","link":"https://stspg.io/psfg42ht97mh","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-03-02T22:49:04.945Z","resolved_at":null,"startTime":"2026-03-02T22:49:04.945Z","endTime":null,"updatedAt":"2026-04-02T18:07:08.590Z","affectedComponents":["Bahrain (me-south-1)"],"incidentUpdates":[{"id":"w15z9zgh2l8v","status":"monitoring","body":"We are continuing to monitor for any further issues.","incident_id":"pgp51rgy1kqr","created_at":"2026-04-02T18:05:13.531Z","updated_at":"2026-04-02T18:05:13.531Z","display_at":"2026-04-02T18:05:13.531Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain (me-south-1)","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":false,"custom_tweet":null,"tweet_id":null},{"id":"4hk1ntp0yr1j","status":"monitoring","body":"We are continuing to monitor for any further issues.","incident_id":"pgp51rgy1kqr","created_at":"2026-03-03T19:06:09.120Z","updated_at":"2026-03-03T19:06:09.120Z","display_at":"2026-03-03T19:06:09.120Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain(me-south-1)","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"grylw90jljpn","status":"monitoring","body":"We are continuing to monitor for any further issues.","incident_id":"pgp51rgy1kqr","created_at":"2026-03-03T03:10:57.034Z","updated_at":"2026-03-03T03:10:57.034Z","display_at":"2026-03-03T03:10:57.034Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain(me-south-1)","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"r6npwrwtnz60","status":"monitoring","body":"AWS  Middle East(Bahrain) outage impacting Cloud NGFW Services.\nWe are aware of power outage in AWS Bahrain region. We are evaluating the impact on Cloud NGFW services in this region. Customers may experience failures to deploy new resources in this region.\nOngoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the AWS Status Page: https://health.aws.amazon.com/health/status?path=service-history\nNext Update: 5:00PM 3/03/2026 UTC.","incident_id":"pgp51rgy1kqr","created_at":"2026-03-02T22:49:05.040Z","updated_at":"2026-03-03T13:00:39.298Z","display_at":"2026-03-02T22:49:05.000Z","affected_components":[{"code":"4xf4jf8sp7yk","name":"Cloud NGFW for AWS - Bahrain(me-south-1)","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"pgp51rgy1kqr","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-03-02T22:49:04.945Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/a6b43a3d-15ca-4e4e-9c23-3c1e6d91cbfd","title":"Email Delivery Failure – System Outbound Block","description":"[Resolved] The issue has been mitigated and systems are now stable. We’ve marked this incident as resolved, but we will continue to monitor closely to ensure full recovery and prevent recurrence.","pubDate":"Wed, 01 Oct 2025 12:13:19 -0700","link":"https://status.lastpass.com/incidents/a6b43a3d-15ca-4e4e-9c23-3c1e6d91cbfd","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 01 Oct 2025 12:13:19 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 01 Oct 2025 12:13:19 -0700","endTime":null,"updatedAt":"Wed, 01 Oct 2025 12:13:19 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/a6b43a3d-15ca-4e4e-9c23-3c1e6d91cbfd","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2025-10-01T19:13:19.000Z","_parsedEndTime":null}],"remainingOngoingCount":37,"remainingOngoingIncidents":[{"id":"sxqfl8d1wx7p","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Sydney</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-07-09T04:22:20.256Z","link":"https://stspg.io/c9rfpg8btwr9","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-09T04:22:20.256Z","resolved_at":null,"startTime":"2026-07-09T04:22:20.256Z","endTime":null,"updatedAt":"2026-07-09T04:22:20.261Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"9jj6y963d7n3","status":"investigating","body":"<p><strong>Update:</strong> Changes to Locations</p><p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Hong Kong, Jakarta, Mumbai, Osaka, Seoul, Singapore, Sydney, Taipei, Tokyo</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"sxqfl8d1wx7p","created_at":"2026-07-09T04:22:20.256Z","updated_at":"2026-07-09T04:22:20.256Z","display_at":"2026-07-09T04:22:20.256Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"x4hl83zt5jvd","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Sydney</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"sxqfl8d1wx7p","created_at":"2026-06-17T22:53:18.986Z","updated_at":"2026-06-17T22:53:18.986Z","display_at":"2026-06-17T22:53:18.986Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"sxqfl8d1wx7p","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-09T04:22:20.256Z","_parsedEndTime":null},{"id":"707f1mcwyk1d","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Eemshaven</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-07-09T04:13:48.039Z","link":"https://stspg.io/z4p9sdn8c597","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-09T04:13:48.039Z","resolved_at":null,"startTime":"2026-07-09T04:13:48.039Z","endTime":null,"updatedAt":"2026-07-09T04:13:48.044Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"5d9w68bm9rv8","status":"investigating","body":"<p><strong>Update:</strong> Changes to Locations</p><p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Berlin, Eemshaven, Frankfurt, London, Madrid, Milan, Paris, Warsaw, Zurich</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"707f1mcwyk1d","created_at":"2026-07-09T04:13:48.039Z","updated_at":"2026-07-09T04:13:48.039Z","display_at":"2026-07-09T04:13:48.039Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"c74r5w9brdxf","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Eemshaven</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"707f1mcwyk1d","created_at":"2026-06-17T22:53:14.034Z","updated_at":"2026-06-17T22:53:14.034Z","display_at":"2026-06-17T22:53:14.034Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"707f1mcwyk1d","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-09T04:13:48.039Z","_parsedEndTime":null},{"id":"gznlrf0m50sc","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Council Bluffs</p><p><strong>Impact:</strong></p><p>Email notifications are temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-07-09T04:03:48.365Z","link":"https://stspg.io/d74370c4p2k8","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-09T04:03:48.365Z","resolved_at":null,"startTime":"2026-07-09T04:03:48.365Z","endTime":null,"updatedAt":"2026-07-09T04:03:48.370Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"xq4mf1bf7gtw","status":"investigating","body":"<p><strong>Update:</strong> Changes to Locations</p><p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Council Bluffs, Montreal</p><p><strong>Impact:</strong></p><p>Email notifications are temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"gznlrf0m50sc","created_at":"2026-07-09T04:03:48.365Z","updated_at":"2026-07-09T04:03:48.365Z","display_at":"2026-07-09T04:03:48.365Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"ptfv4pvd6f9w","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Council Bluffs</p><p><strong>Impact:</strong></p><p>Email notifications are temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"gznlrf0m50sc","created_at":"2026-06-17T22:49:21.477Z","updated_at":"2026-06-17T22:49:21.477Z","display_at":"2026-06-17T22:49:21.477Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"gznlrf0m50sc","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-07-09T04:03:48.365Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/dz929wm74wdw","title":"Wireless node Los Angeles - TMobile 5G offline","description":"<p> <small>Jul <var data-var='date'> 8</var>, <var data-var='time'>22:57</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Wireless node Los Angeles - TMobile 5G will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Wed, 08 Jul 2026 22:57:22 +0000","link":"https://lmstatus.catchpoint.com/incidents/dz929wm74wdw","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-08T22:57:00.000Z","resolved_at":null,"startTime":"2026-07-08T22:57:00.000Z","endTime":null,"updatedAt":"2026-07-08T22:57:00.000Z","location":null,"country":null,"provider":null,"nodeType":"wireless","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-08T22:57:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/6l0hfdhjg8z3","title":"Last Mile node LM - Woburn, US - Verizon offline","description":"<p> <small>Jul <var data-var='date'> 5</var>, <var data-var='time'>16:54</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Woburn, US - Verizon will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Sun, 05 Jul 2026 16:54:13 +0000","link":"https://lmstatus.catchpoint.com/incidents/6l0hfdhjg8z3","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-05T16:54:00.000Z","resolved_at":null,"startTime":"2026-07-05T16:54:00.000Z","endTime":null,"updatedAt":"2026-07-05T16:54:00.000Z","location":"Woburn","country":"US","provider":"Verizon offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-05T16:54:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/hk252yzgvb41","title":"Last Mile node LM - Amritsar, IN - Airtel offline","description":"<p> <small>Jul <var data-var='date'> 4</var>, <var data-var='time'>10:56</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Amritsar, IN - Airtel will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Sat, 04 Jul 2026 10:56:47 +0000","link":"https://lmstatus.catchpoint.com/incidents/hk252yzgvb41","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-04T10:56:00.000Z","resolved_at":null,"startTime":"2026-07-04T10:56:00.000Z","endTime":null,"updatedAt":"2026-07-04T10:56:00.000Z","location":"Amritsar","country":"IN","provider":"Airtel offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-04T10:56:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/t2lplmd0mdx3","title":"Last Mile node LM - Suwanee, US - AT&T offline","description":"<p> <small>Jul <var data-var='date'> 2</var>, <var data-var='time'>18:28</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Suwanee, US - AT&T will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Thu, 02 Jul 2026 18:28:43 +0000","link":"https://lmstatus.catchpoint.com/incidents/t2lplmd0mdx3","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-07-02T18:28:00.000Z","resolved_at":null,"startTime":"2026-07-02T18:28:00.000Z","endTime":null,"updatedAt":"2026-07-02T18:28:00.000Z","location":"Suwanee","country":"US","provider":"AT&T offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-07-02T18:28:00.000Z","_parsedEndTime":null},{"id":"betterstack-status-report-939240","guid":"betterstack-status-report-939240","title":"Elevated error rate – AWS CDN (Singapore)","description":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","pubDate":"2026-06-30T07:58:00.000Z","link":"https://status.huggingface.co/incident/939240","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-30T07:58:00.000Z","resolved_at":null,"started_at":"2026-06-30T07:58:00.000Z","startTime":"2026-06-30T07:58:00.000Z","endTime":null,"updatedAt":"2026-06-30T07:58:00.000Z","incidentUpdates":[{"body":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","created_at":"2026-06-30T07:58:00.000Z","status":"investigating"}],"affectedComponents":[{"name":"Elevated error rate – AWS CDN (Singapore)"}],"originalData":{"rssUpdates":[{"title":"Elevated error rate – AWS CDN (Singapore)","link":"https://status.huggingface.co/incident/939240","pubDate":"Tue, 30 Jun 2026 07:58:00 -0000","guid":"https://status.huggingface.co/incident/939240#3c97443b5b5c62a6894d2a3ed7e14e1d53cba1565da2ab0cd604683de7b57b6a","description":"Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-30T08:37:01.236Z","lastUpdated":"2026-06-30T08:37:01.236Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":"939240"},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-06-30T07:58:00.000Z","_parsedEndTime":null},{"title":"Intermittent DNS Resolution Failures for Wildcard Domains","link":"https://trust.zscaler.com/posts/30451","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Wed, 01 Jul 2026 22:55:15 UTC</span></p><p>Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 22:57:26 UTC</span></p><p>Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:18 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:00:34 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-5\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:02:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","pubDate":"Wed, 01 Jul 2026 17:42:58 GMT","guid":"30451 at https://trust.zscaler.com","id":"30451","clouds":["zscaler.net","zscalertwo.net","zscloud.net","zscalerthree.net"],"updates":[{"time":"Wed, 01 Jul 2026 22:55:15 UTC","update":"Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Thu, 02 Jul 2026 22:57:26 UTC","update":"Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:18 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:00:34 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:02:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":[{"time":"Fri, 10 Jul 2026 06:02:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"root_cause":"","startTime":"Tue, 30 Jun 2026 02:50:00 GMT","endTime":null,"eventType":"Service Degradation","customerImpact":"Customers may experience intermittent DNS resolution failures on both Private Service Edges and Public Service Edges when accessing wildcard domains that resolve to more than 256 IP addresses.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":{"name":"Recent incident","domain":"https://trust.zscaler.com"},"current_status":"In Progress","originalData":{"id":"30451","title":"Intermittent DNS Resolution Failures for Wildcard Domains","clouds":"[Circular Reference]","link":"https://trust.zscaler.com/posts/30451","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Wed, 01 Jul 2026 22:55:15 UTC</span></p><p>Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 22:57:26 UTC</span></p><p>Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:18 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:00:34 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-5\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:02:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","updates":[{"time":"Wed, 01 Jul 2026 22:55:15 UTC","update":"Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Thu, 02 Jul 2026 22:57:26 UTC","update":"Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:18 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:00:34 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the intermittent DNS resolution issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:02:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Wed, 01 Jul 2026 17:42:58 GMT","resolved_date":null,"startTime":"Tue, 30 Jun 2026 02:50:00 GMT","endTime":"","eventType":"Service Degradation","customerImpact":"Customers may experience intermittent DNS resolution failures on both Private Service Edges and Public Service Edges when accessing wildcard domains that resolve to more than 256 IP addresses.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":"[Circular Reference]","current_status":"In Progress","how_found":"Customer Reported"},"feedUrl":"https://trust.zscaler.com/rss-feed/incidents?_format=json","trustEnvironment":"Commercial","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-07-01T18:12:00.996Z","lastUpdated":"2026-07-10T06:07:00.158Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"major","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-06-30T02:50:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/rsmwp7jcy0pd","title":"Last Mile node LM - Lucca, IT - Wind3 offline","description":"<p> <small>Jun <var data-var='date'>29</var>, <var data-var='time'>21:18</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Lucca, IT - Wind3 will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Mon, 29 Jun 2026 21:18:15 +0000","link":"https://lmstatus.catchpoint.com/incidents/rsmwp7jcy0pd","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-29T21:18:00.000Z","resolved_at":null,"startTime":"2026-06-29T21:18:00.000Z","endTime":null,"updatedAt":"2026-06-29T21:18:00.000Z","location":"Lucca","country":"IT","provider":"Wind3 offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-29T21:18:00.000Z","_parsedEndTime":null},{"title":"Private Application Session Timeouts with ZIA Inspection Enabled","link":"https://trust.zscaler.com/posts/30486","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 21:12:46 UTC</span></p><p>Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:59 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:01:15 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:04:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","pubDate":"Thu, 02 Jul 2026 20:35:16 GMT","guid":"30486 at https://trust.zscaler.com","id":"30486","clouds":["zscaler.net","zscalertwo.net","zscloud.net","zscalerthree.net"],"updates":[{"time":"Thu, 02 Jul 2026 21:12:46 UTC","update":"Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:59 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:01:15 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:04:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":[{"time":"Fri, 10 Jul 2026 06:04:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"root_cause":"","startTime":"Mon, 29 Jun 2026 13:00:00 GMT","endTime":null,"eventType":"Service Degradation","customerImpact":"A limited subset of customers using ZPA with ZIA Inspection enabled for certain private application traffic may experience connection timeouts or dropped sessions for SSH and other long-lived, non-HTTP private application sessions inspected by ZIA.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":{"name":"Recent incident","domain":"https://trust.zscaler.com"},"current_status":"In Progress","originalData":{"id":"30486","title":"Private Application Session Timeouts with ZIA Inspection Enabled","clouds":"[Circular Reference]","link":"https://trust.zscaler.com/posts/30486","description":"<div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Thu, 02 Jul 2026 21:12:46 UTC</span></p><p>Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.</p></div><div class=\"update-list update-2\"><p class=\"zs-update\">Update - <span class=\"report-time\">Sun, 05 Jul 2026 09:42:59 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.</p></div><div class=\"update-list update-3\"><p class=\"zs-update\">Update - <span class=\"report-time\">Tue, 07 Jul 2026 08:01:15 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.</p></div><div class=\"update-list update-4\"><p class=\"zs-update\">Update - <span class=\"report-time\">Fri, 10 Jul 2026 06:04:36 UTC</span></p><p>Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.</p></div>","updates":[{"time":"Thu, 02 Jul 2026 21:12:46 UTC","update":"Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.","status":"In-Progress"},{"time":"Sun, 05 Jul 2026 09:42:59 UTC","update":"Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.","status":"In-Progress"},{"time":"Tue, 07 Jul 2026 08:01:15 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address this issue affecting some customers. Deployment has been completed across all ZS2 infrastructure, with significant progress made across ZSNet, ZSCloud, and ZS3. Deployment across the remaining cloud infrastructure in APAC, EMEA, and AMER is ongoing, and Zscaler will provide further updates as progress continues.","status":"In-Progress"},{"time":"Fri, 10 Jul 2026 06:04:36 UTC","update":"Zscaler continues the phased deployment of the corrective software update to address the issue affecting some customers. Deployment is now complete across ZS2, ZS3, and largely complete across ZSNet and ZSCloud infrastructure globally. Zscaler will provide a final update upon completion.","status":"In-Progress"}],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Thu, 02 Jul 2026 20:35:16 GMT","resolved_date":null,"startTime":"Mon, 29 Jun 2026 13:00:00 GMT","endTime":"","eventType":"Service Degradation","customerImpact":"A limited subset of customers using ZPA with ZIA Inspection enabled for certain private application traffic may experience connection timeouts or dropped sessions for SSH and other long-lived, non-HTTP private application sessions inspected by ZIA.","availableWorkaround":"","nextUpdate":"To be provided when additional information is available.","summary":"","category":"[Circular Reference]","current_status":"In Progress","how_found":"Customer Reported"},"feedUrl":"https://trust.zscaler.com/rss-feed/incidents?_format=json","trustEnvironment":"Commercial","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-07-02T20:52:01.540Z","lastUpdated":"2026-07-10T06:07:00.158Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-06-29T13:00:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/3jrd2v3v31pw","title":"Last Mile node LM - Ciudad de México, MX - TotalPlay offline","description":"<p> <small>Jun <var data-var='date'>29</var>, <var data-var='time'>09:23</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Ciudad de México, MX - TotalPlay will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Mon, 29 Jun 2026 09:23:15 +0000","link":"https://lmstatus.catchpoint.com/incidents/3jrd2v3v31pw","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-29T09:23:00.000Z","resolved_at":null,"startTime":"2026-06-29T09:23:00.000Z","endTime":null,"updatedAt":"2026-06-29T09:23:00.000Z","location":"Ciudad de México","country":"MX","provider":"TotalPlay offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-29T09:23:00.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/v2y0tzxjlbvl","title":"Last Mile node LM - Lipa, PH - Converge offline","description":"<p> <small>Jun <var data-var='date'>26</var>, <var data-var='time'>05:58</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Lipa, PH - Converge will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Fri, 26 Jun 2026 05:58:43 +0000","link":"https://lmstatus.catchpoint.com/incidents/v2y0tzxjlbvl","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-26T05:58:00.000Z","resolved_at":null,"startTime":"2026-06-26T05:58:00.000Z","endTime":null,"updatedAt":"2026-06-26T05:58:00.000Z","location":"Lipa","country":"PH","provider":"Converge offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-26T05:58:00.000Z","_parsedEndTime":null},{"title":"Potential CC/BC ZIA Tunnel Flap with Plain UDP Configuration","link":"https://trust.zscaler.us/posts/12856","description":"Zscaler is currently investigating reports of issues with traffic forwarding on its zscalergov.net (FedRAMP Moderate), zscalerten.net (FedRAMP High) Cloud. ","pubDate":"Tue, 23 Jun 2026 21:42:12 GMT","guid":"12856 at https://trust.zscaler.us","id":"12856","clouds":["zscalergov.net (FedRAMP Moderate)","zscalerten.net (FedRAMP High)"],"updates":[],"latest_update":[],"root_cause":"","startTime":"Mon, 22 Jun 2026 21:42:03 GMT","endTime":null,"eventType":"Under Investigation","customerImpact":"Customers with CC/BC groups configured for plain UDP tunnels may experience ZIA tunnel instability (flapping).\r\nTunnels in this configuration may transition between up and down states, potentially causing intermittent connectivity loss for ZIA-bound traffic.","availableWorkaround":"<p>Customers are advised to <strong>reconfigure affected CC/BC groups to use encrypted tunnels (DTLS)</strong> instead of plain UDP. Moving to encrypted tunnels has been confirmed to restore stable ZIA traffic flow.</p><h6>Steps:</h6><ol><li data-list-item-id=\"ef932c92390c59e0d8b1a03ad83c4f3a9\">Identify CC/BC groups currently configured with plain UDP in the group configuration.</li><li data-list-item-id=\"efdaba05d9867137e0959d22ad6e88557\">Update the group tunnel configuration from <strong>UDP</strong> to <strong>DTLS</strong>.</li><li data-list-item-id=\"e751c45636cffc7e4202b0ba8d2b39e03\">Validate that ZIA traffic is passing as expected after the change.</li></ol>","nextUpdate":null,"summary":"Zscaler has identified a potential issue where Cloud Connector (CC) and Branch Connector (BC) ZIA tunnels may flap if the group configuration is set to use plain (unencrypted) UDP tunnels. Affected tunnels may go up or down intermittently, which can result in traffic disruption.","category":{"name":"Recent incident","domain":"https://trust.zscaler.us"},"current_status":"In Progress","originalData":{"id":"12856","title":"Potential CC/BC ZIA Tunnel Flap with Plain UDP Configuration","clouds":"[Circular Reference]","link":"https://trust.zscaler.us/posts/12856","description":"Zscaler is currently investigating reports of issues with traffic forwarding on its zscalergov.net (FedRAMP Moderate), zscalerten.net (FedRAMP High) Cloud. ","updates":[],"latest_update":"[Circular Reference]","root_cause":"","pubDate":"Tue, 23 Jun 2026 21:42:12 GMT","resolved_date":null,"startTime":"Mon, 22 Jun 2026 21:42:03 GMT","endTime":"","eventType":"Under Investigation","customerImpact":"Customers with CC/BC groups configured for plain UDP tunnels may experience ZIA tunnel instability (flapping).\r\nTunnels in this configuration may transition between up and down states, potentially causing intermittent connectivity loss for ZIA-bound traffic.","availableWorkaround":"<p>Customers are advised to <strong>reconfigure affected CC/BC groups to use encrypted tunnels (DTLS)</strong> instead of plain UDP. Moving to encrypted tunnels has been confirmed to restore stable ZIA traffic flow.</p><h6>Steps:</h6><ol><li data-list-item-id=\"ef932c92390c59e0d8b1a03ad83c4f3a9\">Identify CC/BC groups currently configured with plain UDP in the group configuration.</li><li data-list-item-id=\"efdaba05d9867137e0959d22ad6e88557\">Update the group tunnel configuration from <strong>UDP</strong> to <strong>DTLS</strong>.</li><li data-list-item-id=\"e751c45636cffc7e4202b0ba8d2b39e03\">Validate that ZIA traffic is passing as expected after the change.</li></ol>","nextUpdate":"","summary":"Zscaler has identified a potential issue where Cloud Connector (CC) and Branch Connector (BC) ZIA tunnels may flap if the group configuration is set to use plain (unencrypted) UDP tunnels. Affected tunnels may go up or down intermittently, which can result in traffic disruption.","category":"[Circular Reference]","current_status":"In Progress","how_found":"Customer Reported"},"feedUrl":"https://trust.zscaler.us/rss-feed/incidents?_format=json","trustEnvironment":"Government","feedType":"incidents","feedCategory":"trust-portal","feedProduct":"Unknown","feedYear":null,"firstSeen":"2026-06-29T16:34:49.187Z","lastUpdated":"2026-06-29T16:34:49.187Z","vendor":"Zscaler","vendorId":"zscaler","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","_parsedIsResolved":false,"_parsedStartTime":"2026-06-22T21:42:03.000Z","_parsedEndTime":null},{"id":"d2gls1bq9csz","title":"Strata Logging Service : Email notifications temporarily degraded","description":"Status: investigating\n\n<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Johannesburg</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","pubDate":"2026-06-17T23:12:56.780Z","link":"https://stspg.io/xzyvc4hjn9fj","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-17T23:12:56.780Z","resolved_at":null,"startTime":"2026-06-17T23:12:56.780Z","endTime":null,"updatedAt":"2026-06-17T23:12:56.784Z","affectedComponents":["Strata Logging Service"],"incidentUpdates":[{"id":"pryzc1frc4gp","status":"investigating","body":"<p><strong>Status:</strong> Investigating</p><p><strong>Severity:</strong> Degraded</p><p><strong>Locations:</strong> Johannesburg</p><p><strong>Impact:</strong></p><p>Email notifications temporarily degraded</p><p><strong>Workaround:</strong></p><p>N/A</p><br><p>We are actively investigating to restore services.</p>","incident_id":"d2gls1bq9csz","created_at":"2026-06-17T23:12:56.780Z","updated_at":"2026-06-17T23:12:56.780Z","display_at":"2026-06-17T23:12:56.780Z","affected_components":[{"code":"tzlfl78jw7f2","name":"Strata Logging Service","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"d2gls1bq9csz","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-06-17T23:12:56.780Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/6d8cp25cb73c","title":"Last Mile node LM - Stockholm, SE - Comhem AB offline","description":"<p> <small>Jun <var data-var='date'>16</var>, <var data-var='time'>18:26</var> UTC</small><br> <strong>Investigating</strong> - Catchpoint Last Mile node LM - Stockholm, SE - Comhem AB will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available. </p>","pubDate":"Tue, 16 Jun 2026 18:26:38 +0000","link":"https://lmstatus.catchpoint.com/incidents/6d8cp25cb73c","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-16T18:26:00.000Z","resolved_at":null,"startTime":"2026-06-16T18:26:00.000Z","endTime":null,"updatedAt":"2026-06-16T18:26:00.000Z","location":"Stockholm","country":"SE","provider":"Comhem AB offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-06-16T18:26:00.000Z","_parsedEndTime":null},{"id":"betterstack-status-report-919822","guid":"betterstack-status-report-919822","title":"Data serving slowness in Asia region","description":"We are experiencing slowness on large file downloads in Asia region since 7AM UTC. This only affects downloads via the huggingface CLI. Root cause identified and mitigation in progress.","pubDate":"2026-06-10T07:00:00.000Z","link":"https://status.huggingface.co/incident/919822","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-06-10T07:00:00.000Z","resolved_at":null,"started_at":"2026-06-10T07:00:00.000Z","startTime":"2026-06-10T07:00:00.000Z","endTime":null,"updatedAt":"2026-06-10T07:00:00.000Z","incidentUpdates":[{"body":"We are experiencing slowness on large file downloads in Asia region since 7AM UTC. This only affects downloads via the huggingface CLI. Root cause identified and mitigation in progress.","created_at":"2026-06-10T07:00:00.000Z","status":"investigating"}],"affectedComponents":[{"name":"Data serving slowness in Asia region"}],"originalData":{"rssUpdates":[{"title":"Data serving slowness in Asia region","link":"https://status.huggingface.co/incident/919822","pubDate":"Wed, 10 Jun 2026 07:00:00 -0000","guid":"https://status.huggingface.co/incident/919822#5373e8e2d3ac1436fd34c0e6de53ad866f3140aa61335594e99c11e7d469034d","description":"We are experiencing slowness on large file downloads in Asia region since 7AM UTC. This only affects downloads via the huggingface CLI. Root cause identified and mitigation in progress.","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T11:22:00.675Z","lastUpdated":"2026-06-10T11:22:00.675Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":"919822"},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-06-10T07:00:00.000Z","_parsedEndTime":null},{"id":"mg2wqlfm15m8","title":"Prisma Cloud [APP3]: Intermittent login issues","description":"Status: investigating\n\nWe are currently investigating this issue.","pubDate":"2026-05-08T20:51:12.555Z","link":"https://stspg.io/hxz2rl8c96wm","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-05-08T20:51:12.555Z","resolved_at":null,"startTime":"2026-05-08T20:51:12.555Z","endTime":null,"updatedAt":"2026-05-08T20:51:30.092Z","affectedComponents":["Americas - US - app3.prismacloud.io"],"incidentUpdates":[{"id":"l0gzpn1j6nws","status":"identified","body":"The issue has been identified and a fix is being implemented.","incident_id":"mg2wqlfm15m8","created_at":"2026-05-08T20:51:30.089Z","updated_at":"2026-05-08T20:51:30.089Z","display_at":"2026-05-08T20:51:30.089Z","affected_components":[{"code":"6mb2hg5dvyf5","name":"Prisma Cloud - Americas - US - app3.prismacloud.io","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"x7q2szqzfzxj","status":"investigating","body":"We are currently investigating this issue.","incident_id":"mg2wqlfm15m8","created_at":"2026-05-08T20:51:12.555Z","updated_at":"2026-05-08T20:51:12.555Z","display_at":"2026-05-08T20:51:12.555Z","affected_components":[{"code":"6mb2hg5dvyf5","name":"Prisma Cloud - Americas - US - app3.prismacloud.io","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"mg2wqlfm15m8","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-05-08T20:51:12.555Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","guid":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-05-01T21:49:20.000Z","link":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-05-01T21:49:20.000Z","resolved_at":null,"started_at":"2026-05-01T21:49:20.000Z","startTime":"2026-05-01T21:49:20.000Z","endTime":null,"updatedAt":"2026-05-01T21:49:20.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-05-01T21:49:20.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Fri, 01 May 2026 21:49:20 +0000","guid":"https://status.huggingface.co/#a6ff7be929e79561711efdbc544324dd302153872736e220efd3e2666938c816","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-06-10T01:53:42.040Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-05-01T21:49:20.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/32zpqvzfnrlp","title":"Last Mile node LM - Paris, FR - Orange Fiber offline","description":"<p><small>Apr <var data-var='date'>17</var>, <var data-var='time'>14:09</var> UTC</small><br><strong>Investigating</strong> - Catchpoint Last Mile node LM - Paris, FR - Orange Fiber will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available.</p>","pubDate":"Fri, 17 Apr 2026 14:09:09 +0000","link":"https://lmstatus.catchpoint.com/incidents/32zpqvzfnrlp","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-17T14:09:00.000Z","resolved_at":null,"startTime":"2026-04-17T14:09:00.000Z","endTime":null,"updatedAt":"2026-04-17T14:09:00.000Z","location":"Paris","country":"FR","provider":"Orange Fiber offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-04-17T14:09:00.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","guid":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-14T14:53:47.000Z","link":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-14T14:53:47.000Z","resolved_at":null,"started_at":"2026-04-14T14:53:47.000Z","startTime":"2026-04-14T14:53:47.000Z","endTime":null,"updatedAt":"2026-04-14T14:53:47.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-14T14:53:47.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Tue, 14 Apr 2026 14:53:47 +0000","guid":"https://status.huggingface.co/#c8519bbea1e2aaeba6852d5780cbb1aef4d0d8c353d71777a08dbf88bce370b2","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-11T21:37:00.758Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-14T14:53:47.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","guid":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-14T14:38:56.000Z","link":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-14T14:38:56.000Z","resolved_at":null,"started_at":"2026-04-14T14:38:56.000Z","startTime":"2026-04-14T14:38:56.000Z","endTime":null,"updatedAt":"2026-04-14T14:38:56.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-14T14:38:56.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Tue, 14 Apr 2026 14:38:56 +0000","guid":"https://status.huggingface.co/#cca071c1f4ea23ad3e6c3d8e126578c55256873044dec2f95e9c583fba816841","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-11T21:37:00.758Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-14T14:38:56.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","guid":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-09T10:08:32.000Z","link":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-09T10:08:32.000Z","resolved_at":null,"started_at":"2026-04-09T10:08:32.000Z","startTime":"2026-04-09T10:08:32.000Z","endTime":null,"updatedAt":"2026-04-09T10:08:32.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-09T10:08:32.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Thu, 09 Apr 2026 10:08:32 +0000","guid":"https://status.huggingface.co/#3d94b8ef525d0dab9c26f8c2a7f532efed837985dd25c15e7fefdaa0a12643e6","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-08T03:27:00.883Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-09T10:08:32.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","guid":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-09T00:33:29.000Z","link":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-09T00:33:29.000Z","resolved_at":null,"started_at":"2026-04-09T00:33:29.000Z","startTime":"2026-04-09T00:33:29.000Z","endTime":null,"updatedAt":"2026-04-09T00:33:29.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-09T00:33:29.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Thu, 09 Apr 2026 00:33:29 +0000","guid":"https://status.huggingface.co/#a99105e445e2c454289d707130c5d2bf250e0fd0195b048b449e55fba6964287","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-07T03:57:00.627Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-09T00:33:29.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","guid":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-09T00:18:34.000Z","link":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-09T00:18:34.000Z","resolved_at":null,"started_at":"2026-04-09T00:18:34.000Z","startTime":"2026-04-09T00:18:34.000Z","endTime":null,"updatedAt":"2026-04-09T00:18:34.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-09T00:18:34.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Thu, 09 Apr 2026 00:18:34 +0000","guid":"https://status.huggingface.co/#c7f76a6a59700df24353c6f0ff968b58e4bcb91d5e0c461d5b73506568754f93","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-07T03:57:00.627Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-09T00:18:34.000Z","_parsedEndTime":null},{"id":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","guid":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","title":"Git Hosting and Serving outage","description":"Git Hosting and Serving went down","pubDate":"2026-04-08T23:43:32.000Z","link":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-04-08T23:43:32.000Z","resolved_at":null,"started_at":"2026-04-08T23:43:32.000Z","startTime":"2026-04-08T23:43:32.000Z","endTime":null,"updatedAt":"2026-04-08T23:43:32.000Z","incidentUpdates":[{"body":"Git Hosting and Serving went down","created_at":"2026-04-08T23:43:32.000Z","status":"investigating"}],"affectedComponents":[{"name":"Git Hosting and Serving"}],"originalData":{"rssUpdates":[{"title":"Git Hosting and Serving went down","link":"https://status.huggingface.co/","pubDate":"Wed, 08 Apr 2026 23:43:32 +0000","guid":"https://status.huggingface.co/#ed7bd08b67b00cccb0743600058ee51253c365abe9c14f1a8c3d0959690c38e4","description":"Git Hosting and Serving went down","feedType":"incidents","feedCategory":"incidents","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://status.huggingface.co/feed.rss","firstSeen":"2026-06-10T01:53:42.040Z","lastUpdated":"2026-07-07T03:57:00.627Z","_vendorId":"huggingface","vendor":"Hugging Face","vendorId":"huggingface"}],"incidentId":null},"source":"better-stack-feed-rss","vendor":"Hugging Face","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"huggingface","_parsedIsResolved":false,"_parsedStartTime":"2026-04-08T23:43:32.000Z","_parsedEndTime":null},{"id":"tag:status.redhat.com,2005:Incident/28740919","title":"AWS Outage: me-south","description":"<p> <small>Mar <var data-var='date'> 4</var>, <var data-var='time'>04:44</var> UTC</small><br> <strong>Update</strong> - The outage is still ongoing on the AWS side, and recovery efforts are ongoing. AWS is recommending customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region </p> <p> <small>Mar <var data-var='date'> 2</var>, <var data-var='time'>17:52</var> UTC</small><br> <strong>Update</strong> - ROSA clusters deployed in me-south-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation. </p> <p> <small>Mar <var data-var='date'> 2</var>, <var data-var='time'>07:22</var> UTC</small><br> <strong>Identified</strong> - ROSA clusters degraded in me-south due to a localized power issue in mes1-az2.<br />Customers are advised to schedule their workloads into another availability zone.<br /><br />AWS Status Page: https://health.aws.amazon.com/health/status </p>","pubDate":"2026-03-04T04:44:10Z","link":"https://status.redhat.com/incidents/sg4h4gt51xbw","status":"identified","impact":"major","isResolved":false,"created_at":"2026-03-04T04:44:10Z","resolved_at":null,"startTime":"2026-03-04T04:44:10Z","endTime":null,"updatedAt":"2026-03-04T04:44:10Z","guid":"tag:status.redhat.com,2005:Incident/28740919","healthScoreSeverity":"major","healthScoreSeveritySource":"impact","vendorId":"redhat","vendor":"Red Hat","_parsedIsResolved":false,"_parsedStartTime":"2026-03-04T04:44:10.000Z","_parsedEndTime":null},{"title":"Increased Error Rates - Bahrain - Multiple services","link":"https://health.aws.amazon.com/health/status#/arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","description":"We are providing an update on the ongoing service disruption. The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable. Customers should recover their resources in other Regions from remote backups. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.  ","pubDate":"2026-03-02T05:56:27.000Z","guid":"arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","id":"arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","status":"3","serviceName":"Multiple services","regionName":"Bahrain","originalData":{"date":"1772430987","arn":"arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","region_name":"Bahrain","status":"3","service":"multipleservices-me-south-1","service_name":"Multiple services","summary":"Increased Error Rates","event_log":[{"summary":"Increased connectivity issues and API Error Rates","message":"We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.","status":1,"timestamp":1772430987},{"summary":"Increased connectivity issues and API Error Rates","message":"We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. During this time, we are also experiencing delays in propagating DNS changes for Route53 to pops (Points of Presence) in ME-SOUTH-1.  Targeting new launches using RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected.","status":1,"timestamp":1772435343},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work on a localized power issue affecting a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. In the impacted Availability Zone, EC2 Instances, DB Instances, EBS Volumes, and other AWS Services are also experiencing elevated error rates and latencies for some workflows. As part of our recovery effort, we have shifted traffic away from the impacted Availability Zone for most services. We recommend customers utilize one of the other Availability Zones in the ME-SOUTH-1 Region, as existing instances in other AZs remain unaffected by this issue. We are actively working to restore power and connectivity, at which time we will begin recovering affected resources. Currently, we expect recovery to take many hours. We will provide an update by 2:30 AM PST, or sooner if we have additional information to share.","status":1,"timestamp":1772442207},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. At this time, some AWS services have shifted traffic away from the affected Availability Zone and are seeing recovery for their affected operations and workflows. EC2 Instances, EBS Volumes, and other resources impacted in the affected Availability Zone will require a longer recovery timeline. Power has not yet been restored to the affected Availability Zone. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or launch replacement resources in one of the unaffected Availability Zones or an alternate Region. In parallel, we are actively working on reducing the error rates and latencies that some customers are experiencing with EC2 APIs. For now, we recommend continuing to retry any failed API requests. We will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.","status":1,"timestamp":1772448060},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work toward restoring power in the impacted Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. Meanwhile, EC2 instance and networking APIs have been restored for the other Availability Zones. Additionally, we have made improvements to the availability of RDS multi-AZ databases while operating with the impaired Availability Zone. These improvements will help customers create database exports to preserve data, and we recommend customers with databases in the affected Availability Zone consider creating exports as a precautionary measure. EC2 Instances, EBS Volumes, and other resources impacted in the affected Availability Zone will require a longer recovery timeline, as power has not yet been restored. We are expecting recovery to take at least a day, as it requires repair of facilities, cooling and power systems, coordination with local authorities, and careful assessment to ensure the safety of our operators. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. We will provide an update by 11:00 AM PST on March 2, or sooner if we have additional information to share.","status":1,"timestamp":1772461399},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We currently expect our recovery efforts to take at least a day. Our current guidance regarding immediate recovery remains unchanged from our previous update. Customers are able to disassociate Elastic IP addresses from resources in the affected Availability Zone and associate those with resources in the unaffected Availability Zones. This can be done by specifying --allow-reassociation when attempting to associate the Elastic IP to the new resource. We will provide you with further updates by 2:00 PM PST or sooner if new information becomes available.","status":1,"timestamp":1772477520},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue to advise customers to launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. At this time we recommend that customers that are capable of backing up data outside of the region consider doing so. You can view the current status of affected AWS services below. We will provide you with another update by 7:00 PM PST, or sooner if we have additional information to share.","status":1,"timestamp":1772490547},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.\n\nIn the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.\n\nIn parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We recommend that customers with workloads running in the Middle East consider taking action now to backup data and potentially migrate your workloads to alternate AWS Regions. We recommend customers exercise their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 9:00 PM PST on March 2, 2026, or sooner if new information becomes available.","status":1,"timestamp":1772497351},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. AWS infrastructure is designed to be highly resilient, but given the uncertainty of the current situation, we encourage our customers to replicate Amazon S3 and critical data from the ME-SOUTH-1 Region to another AWS Region. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 3 at 3:00 AM PST, or sooner if new information becomes available. \n\nFor more information on Cross-Region Replication, refer [1]. For more information on S3 Batch Replication, see [2]. For a simple script to quickly set up and start S3 Replication, see [3]. If you have questions or concerns, please contact AWS Support [4].\n\n[1] <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html\">https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html</a>\n[2] <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html\">https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html</a>\n[3] <a href=\"https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py\">https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py</a>\n[4] <a href=\"https://aws.amazon.com/support\">https://aws.amazon.com/support</a>","status":1,"timestamp":1772519220},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. The overall state of the region remains largely unchanged from our previous update. At this time, we have no updated guidance on expected timelines for fully restoring power and connectivity. We are taking all necessary steps to support the recovery process. While progress is being made, significant work remains before full restoration is complete. \n\nGiven the ongoing uncertainty, we encourage customers to replicate their Amazon S3 data and other critical data from the ME-SOUTH-1 Region to another AWS Region, using the guidance provided in our previous update. We will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 6:00 AM PST on March 3, or sooner if new information becomes available.","status":1,"timestamp":1772536238},{"summary":"Increased Connectivity Issues and API Error Rates","message":"Recovery efforts in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region are ongoing, with the situation remaining consistent with our last update. We have no change to expected timelines for fully restoring power and connectivity. While progress is being made, significant work remains before full restoration is complete. We continue to recommend customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region.\n\nGiven the extended nature of this event, we continue to encourage customers to replicate Amazon S3 data and other critical workloads from ME-SOUTH-1 to another AWS Region using the guidance shared previously. We will provide our next update by 12:00 PM PST on March 3, or sooner if conditions change.","status":1,"timestamp":1772546577},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.\n\nWe continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.","status":1,"timestamp":1772556000},{"summary":"Increased Connectivity Issues and API Error Rates","message":"We are providing an update on the ongoing service disruption. The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable. Customers should recover their resources in other Regions from remote backups. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.  ","status":3,"timestamp":1777532831}],"impacted_services":{"resourcegroups-me-south-1":{"service_name":"AWS Resource Groups","current":"3","max":"3"},"codepipeline-me-south-1":{"service_name":"AWS CodePipeline","current":"3","max":"3"},"rds-me-south-1":{"service_name":"Amazon Relational Database Service","current":"3","max":"3"},"fargate-me-south-1":{"service_name":"AWS Fargate","current":"3","max":"3"},"awswaf-me-south-1":{"service_name":"AWS WAF","current":"3","max":"3"},"datasync-me-south-1":{"service_name":"AWS DataSync","current":"3","max":"3"},"ecr-me-south-1":{"service_name":"Amazon Elastic Container Registry","current":"3","max":"3"},"lakeformation-me-south-1":{"service_name":"AWS Lake Formation","current":"3","max":"3"},"lambda-me-south-1":{"service_name":"AWS Lambda","current":"3","max":"3"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"firehose-me-south-1":{"service_name":"Amazon Kinesis Firehose","current":"3","max":"3"},"redshift-me-south-1":{"service_name":"Amazon Redshift","current":"3","max":"3"},"sagemaker-me-south-1":{"service_name":"Amazon SageMaker","current":"3","max":"3"},"kafka-me-south-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"3","max":"3"},"transcribe-me-south-1":{"service_name":"Amazon Transcribe","current":"3","max":"3"},"eks-me-south-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"3","max":"3"},"transitgateway-me-south-1":{"service_name":"AWS Transit Gateway","current":"3","max":"3"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"cognito-me-south-1":{"service_name":"Amazon Cognito","current":"3","max":"3"},"cloudshell-me-south-1":{"service_name":"AWS CloudShell","current":"3","max":"3"},"kms-me-south-1":{"service_name":"AWS Key Management Service","current":"3","max":"3"},"emr-me-south-1":{"service_name":"Amazon Elastic MapReduce","current":"3","max":"3"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"ecs-me-south-1":{"service_name":"Amazon Elastic Container Service","current":"3","max":"3"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"1"},"controltower-me-south-1":{"service_name":"AWS Control Tower","current":"3","max":"3"},"fsx-me-south-1":{"service_name":"Amazon FSx","current":"3","max":"3"},"emrserverless-me-south-1":{"service_name":"Amazon EMR Serverless","current":"3","max":"3"},"sns-me-south-1":{"service_name":"Amazon Simple Notification Service","current":"3","max":"3"},"privatelink-me-south-1":{"service_name":"AWS VPCE PrivateLink","current":"3","max":"3"},"elasticsearch-me-south-1":{"service_name":"Amazon OpenSearch Service","current":"3","max":"3"},"elb-me-south-1":{"service_name":"Amazon Elastic Load Balancing","current":"3","max":"3"},"cloudtrail-me-south-1":{"service_name":"AWS CloudTrail","current":"3","max":"3"},"management-console":{"service_name":"AWS Management Console","current":"0","max":"2"},"natgateway-me-south-1":{"service_name":"AWS NAT Gateway","current":"3","max":"3"},"resourcegroupstaggingapi-me-south-1":{"service_name":"AWS Resource Groups Tagging API","current":"3","max":"3"},"cloud9-me-south-1":{"service_name":"AWS Cloud9","current":"3","max":"3"},"scheduler-me-south-1":{"service_name":"Amazon EventBridge Scheduler","current":"3","max":"3"},"state-me-south-1":{"service_name":"AWS Step Functions","current":"3","max":"3"},"elasticfilesystem-me-south-1":{"service_name":"Amazon Elastic File System","current":"3","max":"3"},"cloudhsm-me-south-1":{"service_name":"AWS CloudHSM","current":"3","max":"3"},"cloudwatch-me-south-1":{"service_name":"Amazon CloudWatch","current":"3","max":"3"},"directoryservice-me-south-1":{"service_name":"AWS Directory Service","current":"3","max":"3"},"elasticbeanstalk-me-south-1":{"service_name":"AWS Elastic Beanstalk","current":"3","max":"3"},"glue-me-south-1":{"service_name":"AWS Glue","current":"3","max":"3"},"autoscaling-me-south-1":{"service_name":"Auto Scaling","current":"3","max":"3"},"awsiot-me-south-1":{"service_name":"AWS IoT Core","current":"3","max":"3"},"clientvpn-me-south-1":{"service_name":"AWS Client VPN","current":"3","max":"3"},"servicecatalog-me-south-1":{"service_name":"AWS Service Catalog","current":"3","max":"3"},"storagegateway-me-south-1":{"service_name":"AWS Storage Gateway","current":"3","max":"3"},"computeoptimizer-me-south-1":{"service_name":"AWS Compute Optimizer","current":"3","max":"3"},"kinesis-me-south-1":{"service_name":"Amazon Kinesis Data Streams","current":"3","max":"3"},"dms-me-south-1":{"service_name":"AWS Database Migration Service","current":"3","max":"3"},"awsiotdevicemanagement-me-south-1":{"service_name":"AWS IoT Device Management","current":"3","max":"3"},"networkfirewall-me-south-1":{"service_name":"AWS Network Firewall","current":"3","max":"3"},"inspector-me-south-1":{"service_name":"Amazon Inspector","current":"3","max":"3"},"resourceexplorer-me-south-1":{"service_name":"AWS Resource Explorer","current":"3","max":"3"},"ssmsap-me-south-1":{"service_name":"AWS Systems Manager for SAP","current":"3","max":"3"},"codedeploy-me-south-1":{"service_name":"AWS CodeDeploy","current":"3","max":"3"},"iamidentitycenter-me-south-1":{"service_name":"AWS IAM Identity Center","current":"3","max":"3"},"transfer-me-south-1":{"service_name":"AWS Transfer Family","current":"3","max":"3"},"vpnvpc-me-south-1":{"service_name":"AWS Site-to-Site VPN","current":"3","max":"3"},"events-me-south-1":{"service_name":"Amazon EventBridge","current":"3","max":"3"},"iotdevicedefender-me-south-1":{"service_name":"AWS IoT Device Defender","current":"3","max":"3"},"codebuild-me-south-1":{"service_name":"AWS CodeBuild","current":"3","max":"3"},"elasticache-me-south-1":{"service_name":"Amazon ElastiCache","current":"3","max":"3"},"appsync-me-south-1":{"service_name":"AWS AppSync","current":"3","max":"3"},"drs-me-south-1":{"service_name":"AWS Elastic Disaster Recovery","current":"3","max":"3"},"vpclattice-me-south-1":{"service_name":"Amazon VPC Lattice","current":"3","max":"3"},"cloudformation-me-south-1":{"service_name":"AWS CloudFormation","current":"3","max":"3"},"mq-me-south-1":{"service_name":"Amazon MQ","current":"3","max":"3"},"swf-me-south-1":{"service_name":"Amazon Simple Workflow Service","current":"3","max":"3"},"ec2-me-south-1":{"service_name":"Amazon Elastic Compute Cloud","current":"3","max":"3"}}},"startTime":"2026-03-02T05:56:27.000Z","created_at":"2026-03-02T05:56:27.000Z","feedType":"incidents","feedCategory":"general","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://health.aws.amazon.com/public/currentevents","firstSeen":"2026-03-16T04:03:38.328Z","lastUpdated":"2026-04-30T15:05:01.166Z","vendor":"Amazon","vendorId":"amazon","healthScoreSeverity":"critical","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-03-02T05:56:27.000Z","_parsedEndTime":null},{"title":"Increased Error Rates - UAE - Multiple services","link":"https://health.aws.amazon.com/health/status#/arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","description":"We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months. ","pubDate":"2026-03-01T12:51:25.000Z","guid":"arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","id":"arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","status":"3","serviceName":"Multiple services","regionName":"UAE","originalData":{"date":"1772369485","arn":"arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","region_name":"UAE","status":"3","service":"multipleservices-me-central-1","service_name":"Multiple services","summary":"Increased Error Rates","event_log":[{"summary":"Increased Error Rates","message":"We are investigating issues with AWS services in the ME-CENTRAL-1 Region.","status":1,"timestamp":1772369485},{"summary":"Increased Error Rates","message":"We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. Targeting new launches using RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected.","status":1,"timestamp":1772371152},{"summary":"Increased Error Rates","message":"We can confirm that a localized power issue has affected a single Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). EC2 Instances, DB Instances, EBS Volumes, and others resources are currently unavailable and will experience connectivity issues at this time. Other AWS Services are also experiencing error rates and latencies for some workflows. We have weighed away traffic for most services at this time. We recommend customers utilize one of the other Availability Zones in the ME-CENTRAL-1 Region at this time, as existing instances in other AZ's remain unaffected by this issue. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. We will provide an update by 7:15 AM PST, or sooner if we have additional information to share.","status":1,"timestamp":1772374140},{"summary":"Increased Error Rates","message":"We wanted to provide some additional information on the isolated power issue. At this time, most AWS Services have weighted away from the affected Availability Zone (mec1-az2) and are seeing recovery for their affected operations and workflows. For EC2 Instances, EBS Volumes, and other resources that are impacted in the affected Zone, we will have a longer tail of recovery. At this time, power has not yet been restored to the affected AZ. For now, we recommend continuing to retry any failed API requests. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources by launching replacement resources in one of the unaffected zones, or an alternate region. As of this time, recovery is still several hours away. We will provide an update by 8:30 AM PST, or sooner if we have additional information to share.","status":2,"timestamp":1772377753},{"summary":"Increased Error Rates","message":"We continue to work toward restoring power in the affected Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). In parallel, we are actively working on improving error rates and latencies that some customers are observing for EC2 Networking and EC2 Describe APIs. Due to increased demand in the unaffected Availability Zones, customers may experience longer than usual provisioning times or may need to retry requests for certain instance types, or pick an alternative instance type. We will provide an update by 10:30 AM PST, or sooner if we have additional information to share. ","status":2,"timestamp":1772384340},{"summary":"Increased Error Rates","message":"We want to provide some additional information on the power issue in a single Availability Zone in the ME-CENTRAL-1 Region. At around 4:30 AM PST, one of our Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire. The fire department shut off power to the facility and generators as they worked to put out the fire. We are still awaiting permission to turn the power back on, and once we have, we will ensure we restore power and connectivity safely. It will take several hours to restore connectivity to the impacted AZ. The other AZs in the region are functioning normally. Customers who were running their applications redundantly across the AZs are not impacted by this event. EC2 Instance launches will continue to be impaired in the impacted AZ. We recommend that customers continue to retry any failed API requests. If immediate recovery of an affected resource (EC2 Instance, EBS Volume, RDS DB Instance, etc.) is required, we recommend restoring from your most recent backup, by launching replacement resources in one of the unaffected zones, or an alternate AWS Region. We will provide an update by 12:30 PM PST, or sooner if we have additional information to share.","status":3,"timestamp":1772386871},{"summary":"Increased Error Rates","message":"We are aware that some customers are experiencing errors when calling EC2 APIs, specifically networking related APIs (AllocateAddress, AssociateAddress, DescribeRouteTable, DescribeNetworkInterfaces). We are actively working on multiple paths to mitigate these issues. For customers experiencing throttling errors on the AllocateAddress APIs, we recommend retrying any failed API requests. We are deploying a configuration change to mitigate the AssociateAddress API errors and expect recovery in the next few hours. DescribeRouteTable and DescribeNetworkInterfaces API calls without specifying zone, Interface or Instance IDs are expected to fail until we restore the impacted zone. We recommend customers to pass these IDs explicitly in these API requests. For customers that can, we recommend considering using alternate AWS Regions. We will provide another update by 3:30 PM PST, or sooner if we have more to share.","status":3,"timestamp":1772396043},{"summary":"Increased Error Rates","message":"We are seeing positive signs of recovery for many of the EC2 APIs, such as Describes and AllocateAddress. We recognize that customers are still experiencing errors when attempting to call the AssociateAddress API, and are unable to disassociate addresses from resources that are affected by the underlying power issue. We continue to work on multiple parallel paths to mitigate both of these issues. We recommend continuing to retry requests wherever possible. We expect our current mitigation efforts for these specific issues to complete within the the two to three hours. As we progress with these mitigation efforts, customers will observe higher success rates for these operations. Additionally, we are investigating ways to speed up these specific mitigation efforts, but are ensuring we do so safely. As of this time, power restoration is still several hours away. We will provide another update by 5:30 PM PST, or sooner if we have additional information to share.","status":3,"timestamp":1772404099},{"summary":"Increased Error Rates","message":"We are seeing significant signs of recovery for AssociateAddress requests, and continue to work toward fully mitigating this issue. This combined with the earlier recovery of the AllocateAddress API means customers can now successfully create and associate new network addresses in the unaffected AZs. Other AWS Services are also now observing sustained improvement as a result of the EC2 Networking APIs recovery. We are now focusing on implementing a change that will allow customers to Disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. We expect this specific mitigation to take another hour to complete. We do not have an ETA for power restoration at this time. For customers that can, we recommend using alternate Availability Zones or other AWS Regions where applicable. We will provide another update by 6:30 PM, or sooner if we have additional information to share.","status":3,"timestamp":1772411201},{"summary":"Increased Error Rates","message":"We confirm the recovery of the AssociateAddress API requests. We have also applied a change that enables customers to disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. With these mitigations, customers can now successfully create and associate new network addresses in the unaffected AZs as well as re-associate Elastic IPs from resources in the affected zone to resources in the unaffected zones. We still do not have an ETA for power restoration at this time. For customers that can, we recommend using alternate Availability Zones or other AWS Regions where applicable. We will provide another update by 10:00 PM, or sooner if we have additional information to share.","status":3,"timestamp":1772416907},{"summary":"Increased Error Rates","message":"We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.","status":3,"timestamp":1772431169},{"summary":"Increased Error Rates","message":"We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3). Customers are also experiencing increased EC2 APIs and instance launch errors for the remaining zone (mec1-az1). At this point it is not possible to launch new instances in the region, although existing instances should not be affected in mec1-az1. Other AWS Services, such as DynamoDB and S3 are also experiencing significant error rates and latencies. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. For customers that can, we recommend failing away to another AWS Region at this time. We will provide an update by 12:00 AM PST, or sooner if we have additional information to share.","status":3,"timestamp":1772433960},{"summary":"Increased Error Rates","message":"We continue to work on a localized power issue affecting multiple Availability Zones in the ME-CENTRAL-1 Region (mec1-az2 and mec1-az3). Customers are experiencing increased EC2 API errors and instance launch failures across the region, and it is not currently possible to launch new instances; existing instances in mec1-az1 should not be affected. Amazon DynamoDB and Amazon S3 are also experiencing significant error rates and elevated latencies. We are actively working to restore power and connectivity, after which we will begin recovery of affected resources; full recovery is still expected to be many hours away. We recommend that affected customers failover, and backup any critical data, to another AWS Region. We will provide an update by 2:00 AM PST, or sooner if the situation changes.","status":3,"timestamp":1772441520},{"summary":"Increased Error Rates","message":"We wanted to provide more information on Amazon S3 given that there are two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. Amazon S3 is a regional service and designed to withstand the total loss of a single Availability Zone while maintaining S3's durability and availability. When the mec1-az2 AZ was powered off at approximately 4:00 AM PST on Sunday, March 1, S3 continued to operate normally. As the second AZ became impaired, S3 error rates increased. With two Availability Zones significantly impacted, customers are seeing high failure rates for data ingest and egress. We strongly advise customers to update their applications to ingest S3 data to an alternate AWS Region. As soon as practically possible, we will begin the restoration of our two Availability Zones which will include a careful assessment of data health and any repair of storage if necessary.\n\nIn addition, we can confirm that the AWS Management Console and command line interface (CLI) are disrupted by the failure of two Availability Zones. We continue to work towards recovery across all services, and we will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.","status":3,"timestamp":1772448800},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We are expecting recovery to take at least a day, as it requires repair of facilities, cooling and power systems, coordination with local authorities, and careful assessment to ensure the safety of our operators. EC2, Amazon DynamoDB and other AWS Services continue to experience significant error rates and elevated latencies.\nWe recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Further, we strongly advise customers to update their applications to ingest S3 data to an alternate AWS Region. We will provide an update by 11:00 AM PST on March 2, or sooner if we have additional information to share.","status":3,"timestamp":1772461323},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. The impact is causing elevated errors rates for both the Management Console and CLI. Our current expectation is that recovery will take at least a day to complete. We continue to recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions. We will continue to provide periodic updates on recovery efforts. Our next update will be by 2:00 PM PST or sooner if new information becomes available.","status":3,"timestamp":1772474389},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We have partially restored access to the AWS Management Console, however, some pages will continue to load unsuccessfully until we have recovered core services and power. In parallel to the power and recovery efforts, we are working to restore access to tools and utilities to allow customers to backup and migrate their data. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue advising customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions. We will provide you with another update by 6:00 PM PST, or sooner if new information becomes available.","status":3,"timestamp":1772487370},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.\n\nIn the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.\n\nIn parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We recommend that customers with workloads running in the Middle East consider taking action now to backup data and potentially migrate your workloads to alternate AWS Regions. We recommend customers exercise their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 9:00 PM PST on March 2, 2026, or sooner if new information becomes available.","status":3,"timestamp":1772497188},{"summary":"Increased Error Rates","message":"We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region with a focus on restoring functionality to foundational services. Since our last update we have made incremental progress in recovering the DynamoDB control plane which will not be visible to external customers but are required for the restoration of service. Similarly we have made progress with the S3 control plane. The recovery of these foundational services, when complete, will enable a broad range of dependent AWS services to recover. We still estimate that the recovery time is at least a day before we are able to fully restore power and connectivity. We will provide you with another update by March 3 2:00 AM PST, or sooner if new information becomes available.","status":3,"timestamp":1772514818},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged from our previous update. We continue to work closely with local authorities and are prioritizing the safety of our personnel throughout our recovery efforts. Teams continue to assess the damage to the affected facilities and are working to restore infrastructure impacted by the event.\n\nWith respect to Amazon S3, we are seeing improvement in PUT and LIST availability. We continue to work on improving GET error rates, but full recovery will be dependent on restoring the affected infrastructure, which our teams continue to work toward.\n\nFor Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery efforts. We have not yet seen meaningful improvement in DynamoDB availability, but expect conditions to improve over the coming hours as recovery work progresses.\n\nAmazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region. We will begin relaxing these throttles as soon as we have fully recovered our foundational services and have sufficient capacity to support new launches safely.\n\nThe AWS Management Console is now operational, though customers may continue to experience errors on certain pages and operations as the underlying services work through their recovery. We recommend customers continue to retry requests where possible.\n\nAWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and a number of other AWS services that were impacted by this event remain degraded. The availability of these services is dependent on the recovery of our foundational services — primarily Amazon S3 and Amazon DynamoDB — and we expect to see improvement across these services as that recovery progresses.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 5:00 AM PST on March 3, or sooner if new information becomes available.","status":3,"timestamp":1772528640},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged, though our teams continue to make progress on recovery efforts across multiple workstreams. \n\nFor Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. \n\nThe AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery. We recommend that customers continue to retry requests where possible. \n\nWe strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. \n\nWe will provide another update by March 3 at 10:00 AM PST, or sooner if new information becomes available. ","status":3,"timestamp":1772542694},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams.\n\nFor Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery.\n\nWith the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.\n\nWe continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.","status":3,"timestamp":1772554485},{"summary":"Increased Error Rates","message":"We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months. ","status":3,"timestamp":1777533954}],"impacted_services":{"vpclattice-me-central-1":{"service_name":"Amazon VPC Lattice","current":"3","max":"3"},"iamidentitycenter-me-central-1":{"service_name":"AWS IAM Identity Center","current":"3","max":"3"},"rds-me-central-1":{"service_name":"Amazon Relational Database Service","current":"3","max":"3"},"cloudwatch-me-central-1":{"service_name":"Amazon CloudWatch","current":"3","max":"3"},"signin-me-central-1":{"service_name":"AWS Sign-In","current":"3","max":"3"},"endusermessaging-me-central-1":{"service_name":"AWS End User Messaging","current":"3","max":"3"},"fms-me-central-1":{"service_name":"AWS Firewall Manager","current":"3","max":"3"},"swf-me-central-1":{"service_name":"Amazon Simple Workflow Service","current":"3","max":"3"},"iotdevicedefender-me-central-1":{"service_name":"AWS IoT Device Defender","current":"3","max":"3"},"trafficmirroring-me-central-1":{"service_name":"Traffic Mirroring","current":"3","max":"3"},"natgateway-me-central-1":{"service_name":"AWS NAT Gateway","current":"3","max":"3"},"aps":{"service_name":"Amazon Managed Service for Prometheus","current":"3","max":"3"},"batch-me-central-1":{"service_name":"AWS Batch","current":"3","max":"3"},"datasync-me-central-1":{"service_name":"AWS DataSync","current":"3","max":"3"},"directconnect-me-central-1":{"service_name":"AWS Direct Connect","current":"3","max":"3"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"secretsmanager-me-central-1":{"service_name":"AWS Secrets Manager","current":"3","max":"3"},"emr-me-central-1":{"service_name":"Amazon Elastic MapReduce","current":"3","max":"3"},"fsx-me-central-1":{"service_name":"Amazon FSx","current":"3","max":"3"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"2"},"cloudtrail-me-central-1":{"service_name":"AWS CloudTrail","current":"3","max":"3"},"grafana":{"service_name":"Amazon Managed Grafana","current":"3","max":"3"},"vpc-me-central-1":{"service_name":"Amazon Virtual Private Cloud","current":"3","max":"3"},"resourcegroups-me-central-1":{"service_name":"AWS Resource Groups","current":"3","max":"3"},"verifiedaccess":{"service_name":"AWS Verified Access","current":"3","max":"3"},"resourcegroupstaggingapi-me-central-1":{"service_name":"AWS Resource Groups Tagging API","current":"3","max":"3"},"management-console":{"service_name":"AWS Management Console","current":"0","max":"3"},"s3-me-central-1":{"service_name":"Amazon Simple Storage Service","current":"3","max":"3"},"cloudhsm-me-central-1":{"service_name":"AWS CloudHSM","current":"3","max":"3"},"elasticsearch-me-central-1":{"service_name":"Amazon OpenSearch Service","current":"3","max":"3"},"cloudshell-me-central-1":{"service_name":"AWS CloudShell","current":"3","max":"3"},"amplify":{"service_name":"AWS Amplify","current":"3","max":"3"},"transfer-me-central-1":{"service_name":"AWS Transfer Family","current":"3","max":"3"},"elasticbeanstalk-me-central-1":{"service_name":"AWS Elastic Beanstalk","current":"3","max":"3"},"awswaf-me-central-1":{"service_name":"AWS WAF","current":"3","max":"3"},"emrserverless-me-central-1":{"service_name":"Amazon EMR Serverless","current":"3","max":"3"},"config-me-central-1":{"service_name":"AWS Config","current":"3","max":"3"},"ecs-me-central-1":{"service_name":"Amazon Elastic Container Service","current":"3","max":"3"},"kinesisanalytics-me-central-1":{"service_name":"Amazon Managed Service for Apache Flink","current":"3","max":"3"},"glue-me-central-1":{"service_name":"AWS Glue","current":"3","max":"3"},"reachabilityanalyzer":{"service_name":"Reachability Analyzer","current":"3","max":"3"},"security-ir-me-central-1":{"service_name":"AWS Security Incident Response","current":"3","max":"3"},"ssmsap-me-central-1":{"service_name":"AWS Systems Manager for SAP","current":"3","max":"3"},"eks-me-central-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"3","max":"3"},"resourceexplorer-me-central-1":{"service_name":"AWS Resource Explorer","current":"3","max":"3"},"elasticache-me-central-1":{"service_name":"Amazon ElastiCache","current":"3","max":"3"},"certificatemanager-me-central-1":{"service_name":"AWS Certificate Manager","current":"3","max":"3"},"awsiotdevicemanagement-me-central-1":{"service_name":"AWS IoT Device Management","current":"3","max":"3"},"neptune-db-me-central-1":{"service_name":"Amazon Neptune","current":"3","max":"3"},"docdb-me-central-1":{"service_name":"Amazon DocumentDB","current":"3","max":"3"},"state-me-central-1":{"service_name":"AWS Step Functions","current":"3","max":"3"},"inspector-me-central-1":{"service_name":"Amazon Inspector","current":"3","max":"3"},"controltower-me-central-1":{"service_name":"AWS Control Tower","current":"3","max":"3"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"servicecatalog-me-central-1":{"service_name":"AWS Service Catalog","current":"3","max":"3"},"kafka-me-central-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"3","max":"3"},"lakeformation-me-central-1":{"service_name":"AWS Lake Formation","current":"3","max":"3"},"licensemanager-me-central-1":{"service_name":"AWS License Manager","current":"3","max":"3"},"fargate-me-central-1":{"service_name":"AWS Fargate","current":"3","max":"3"},"ec2-me-central-1":{"service_name":"Amazon Elastic Compute Cloud","current":"3","max":"3"},"kms-me-central-1":{"service_name":"AWS Key Management Service","current":"3","max":"3"},"servicediscovery-me-central-1":{"service_name":"AWS Cloud Map","current":"3","max":"3"},"sts-me-central-1":{"service_name":"AWS Security Token Service","current":"3","max":"3"},"workspaces":{"service_name":"Amazon WorkSpaces","current":"3","max":"3"},"appconfig-me-central-1":{"service_name":"AWS AppConfig","current":"3","max":"3"},"clientvpn-me-central-1":{"service_name":"AWS Client VPN","current":"3","max":"3"},"redshift-me-central-1":{"service_name":"Amazon Redshift","current":"3","max":"3"},"firehose-me-central-1":{"service_name":"Amazon Kinesis Firehose","current":"3","max":"3"},"ipam-me-central-1":{"service_name":"Amazon VPC IP Address Manager","current":"3","max":"3"},"elb-me-central-1":{"service_name":"Amazon Elastic Load Balancing","current":"3","max":"3"},"scheduler-me-central-1":{"service_name":"Amazon EventBridge Scheduler","current":"3","max":"3"},"privatelink-me-central-1":{"service_name":"AWS VPCE PrivateLink","current":"3","max":"3"},"lambda-me-central-1":{"service_name":"AWS Lambda","current":"3","max":"3"},"sqs-me-central-1":{"service_name":"Amazon Simple Queue Service","current":"3","max":"3"},"mq-me-central-1":{"service_name":"Amazon MQ","current":"3","max":"3"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"elemental-me-central-1":{"service_name":"AWS Elemental","current":"3","max":"3"},"storagegateway-me-central-1":{"service_name":"AWS Storage Gateway","current":"3","max":"3"},"dynamodb-me-central-1":{"service_name":"Amazon DynamoDB","current":"3","max":"3"},"athena-me-central-1":{"service_name":"Amazon Athena","current":"3","max":"3"},"appsync-me-central-1":{"service_name":"AWS AppSync","current":"3","max":"3"},"kinesis-me-central-1":{"service_name":"Amazon Kinesis Data Streams","current":"3","max":"3"},"directoryservice-me-central-1":{"service_name":"AWS Directory Service","current":"3","max":"3"},"events-me-central-1":{"service_name":"Amazon EventBridge","current":"3","max":"3"},"dms-me-central-1":{"service_name":"AWS Database Migration Service","current":"3","max":"3"},"cognito-me-central-1":{"service_name":"Amazon Cognito","current":"3","max":"3"},"ec2systemsmanager-me-central-1":{"service_name":"AWS Systems Manager","current":"3","max":"3"},"imagebuilder-me-central-1":{"service_name":"EC2 Image Builder","current":"3","max":"3"},"drs-me-central-1":{"service_name":"AWS Elastic Disaster Recovery","current":"3","max":"3"},"glacier-me-central-1":{"service_name":"Amazon Glacier","current":"3","max":"3"},"transitgateway-me-central-1":{"service_name":"AWS Transit Gateway","current":"3","max":"3"},"cloudformation-me-central-1":{"service_name":"AWS CloudFormation","current":"3","max":"3"},"acm-pca-me-central-1":{"service_name":"AWS Private Certificate Authority","current":"3","max":"3"},"networkfirewall-me-central-1":{"service_name":"AWS Network Firewall","current":"3","max":"3"},"awsiot-me-central-1":{"service_name":"AWS IoT Core","current":"3","max":"3"},"computeoptimizer-me-central-1":{"service_name":"AWS Compute Optimizer","current":"3","max":"3"},"mgn-me-central-1":{"service_name":"AWS Application Migration Service","current":"3","max":"3"},"codedeploy-me-central-1":{"service_name":"AWS CodeDeploy","current":"3","max":"3"},"iamrolesanywhere-me-central-1":{"service_name":"AWS Identity and Access Management Roles Anywhere","current":"3","max":"3"},"securityhub-me-central-1":{"service_name":"AWS Security Hub","current":"3","max":"3"},"autoscaling-me-central-1":{"service_name":"Auto Scaling","current":"3","max":"3"},"backup-me-central-1":{"service_name":"AWS Backup","current":"3","max":"3"},"ecr-me-central-1":{"service_name":"Amazon Elastic Container Registry","current":"3","max":"3"},"codecommit-me-central-1":{"service_name":"AWS CodeCommit","current":"3","max":"3"},"guardduty-me-central-1":{"service_name":"Amazon GuardDuty","current":"3","max":"3"},"apigateway-me-central-1":{"service_name":"Amazon API Gateway","current":"3","max":"3"},"sagemaker-me-central-1":{"service_name":"Amazon SageMaker","current":"3","max":"3"},"vpnvpc-me-central-1":{"service_name":"AWS Site-to-Site VPN","current":"3","max":"3"},"elasticfilesystem-me-central-1":{"service_name":"Amazon Elastic File System","current":"3","max":"3"},"ses-me-central-1":{"service_name":"Amazon Simple Email Service","current":"3","max":"3"},"sns-me-central-1":{"service_name":"Amazon Simple Notification Service","current":"3","max":"3"},"codepipeline-me-central-1":{"service_name":"AWS CodePipeline","current":"3","max":"3"},"codebuild-me-central-1":{"service_name":"AWS CodeBuild","current":"3","max":"3"}}},"startTime":"2026-03-01T12:51:25.000Z","created_at":"2026-03-01T12:51:25.000Z","feedType":"incidents","feedCategory":"general","feedProduct":"Unknown","feedYear":null,"feedUrl":"https://health.aws.amazon.com/public/currentevents","firstSeen":"2026-03-16T04:03:38.328Z","lastUpdated":"2026-04-30T15:05:01.166Z","vendor":"Amazon","vendorId":"amazon","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","_parsedIsResolved":false,"_parsedStartTime":"2026-03-01T12:51:25.000Z","_parsedEndTime":null},{"id":"https://lmstatus.catchpoint.com/incidents/w05fqn4qfdqp","title":"Last Mile node LM - Paris, FR - Orange ADSL offline","description":"<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>04:08</var> UTC</small><br><strong>Investigating</strong> - Catchpoint Last Mile node LM - Paris, FR - Orange ADSL will not run tests due to an issue at Last Mile site.<br />We will update the status as soon as there is additional information available.</p>","pubDate":"Sun, 01 Mar 2026 04:08:16 +0000","link":"https://lmstatus.catchpoint.com/incidents/w05fqn4qfdqp","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-03-01T04:08:00.000Z","resolved_at":null,"startTime":"2026-03-01T04:08:00.000Z","endTime":null,"updatedAt":"2026-03-01T04:08:00.000Z","location":"Paris","country":"FR","provider":"Orange ADSL offline","nodeType":"last-mile","vendor":"Catchpoint","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"catchpoint","_parsedIsResolved":false,"_parsedStartTime":"2026-03-01T04:08:00.000Z","_parsedEndTime":null},{"id":"805chf9k0rvx","title":"\"No asset scanned\" error on Connector health dashboard","description":"Status: identified\n\nWe've had an outage on the metrics which impacts Data Security > Dashboard > Connector health and Data Security > Application \"No. Asset Scanned...\"","pubDate":"2026-02-26T17:14:16.185Z","link":"https://stspg.io/58fyt27pycjd","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-02-26T17:14:16.185Z","resolved_at":null,"startTime":"2026-02-26T17:14:16.185Z","endTime":null,"updatedAt":"2026-02-26T17:14:33.788Z","affectedComponents":["SaaS API - North America","SaaS API - Singapore","SaaS API - Frankfurt","SaaS API - India","SaaS API - Australia","SaaS API - London","SaaS API - Japan"],"incidentUpdates":[{"id":"yj2f58pmlnsj","status":"identified","body":"We've had an outage on the metrics which impacts Data Security > Dashboard > Connector health and Data Security > Application \"No. Asset Scanned...\"","incident_id":"805chf9k0rvx","created_at":"2026-02-26T17:14:16.391Z","updated_at":"2026-02-26T17:14:16.391Z","display_at":"2026-02-26T17:14:16.391Z","affected_components":[{"code":"bnljkq76h9cy","name":"Data Security (SaaS Security API) - SaaS API - North America","old_status":"operational","new_status":"partial_outage"},{"code":"lbbl8wqdvz36","name":"Data Security (SaaS Security API) - SaaS API - Singapore","old_status":"operational","new_status":"partial_outage"},{"code":"kxy3h1vwnn9x","name":"Data Security (SaaS Security API) - SaaS API - Frankfurt","old_status":"operational","new_status":"partial_outage"},{"code":"w4d208jmwv95","name":"Data Security (SaaS Security API) - SaaS API - India","old_status":"operational","new_status":"partial_outage"},{"code":"h3wnt9g353kw","name":"Data Security (SaaS Security API) - SaaS API - Australia","old_status":"operational","new_status":"partial_outage"},{"code":"2wr4vkwbp1g8","name":"Data Security (SaaS Security API) - SaaS API - London","old_status":"operational","new_status":"partial_outage"},{"code":"5mbh3wj9xvz4","name":"Data Security (SaaS Security API) - SaaS API - Japan","old_status":"operational","new_status":"partial_outage"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"guid":"805chf9k0rvx","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-02-26T17:14:16.185Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/5e247026-cf08-4cdc-a1db-21a23e8c5f82","title":"Degraded Performance on LastPass Marketing Website","description":"[Resolved] Systems are operational and the incident is resolved","pubDate":"Wed, 29 Oct 2025 17:04:02 -0700","link":"https://status.lastpass.com/incidents/5e247026-cf08-4cdc-a1db-21a23e8c5f82","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 29 Oct 2025 17:04:02 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 29 Oct 2025 17:04:02 -0700","endTime":null,"updatedAt":"Wed, 29 Oct 2025 17:04:02 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/5e247026-cf08-4cdc-a1db-21a23e8c5f82","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2025-10-30T00:04:02.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/5095916e-b039-4758-9468-5256c8ba4337","title":"LastPass - Login issues for Lastpass","description":"[Resolved] On 04/19/2023 , from approximately 13:33 UTC until 13:56 UTC, a small subset of Lastpass users would have noticed a message \"unknown error occurred\" when trying to login to the application.  Our engineers have corrected the issue and we confirm that all services are functional.  We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.","pubDate":"Wed, 19 Apr 2023 08:17:43 -0700","link":"https://status.lastpass.com/incidents/5095916e-b039-4758-9468-5256c8ba4337","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 19 Apr 2023 08:17:43 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 19 Apr 2023 08:17:43 -0700","endTime":null,"updatedAt":"Wed, 19 Apr 2023 08:17:43 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/5095916e-b039-4758-9468-5256c8ba4337","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2023-04-19T15:17:43.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/768d9296-5a2a-4d37-8f8a-ebfe4f30e71d","title":"LastPass - Intermittent login failures","description":"[Resolved] On 11/06/2019, from 12:00 until 12:10 UTC, some LastPass users may have experienced intermittent authentication failures and errors while logging in. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize any future recurrences.","pubDate":"Wed, 06 Nov 2019 04:31:32 -0800","link":"https://status.lastpass.com/incidents/768d9296-5a2a-4d37-8f8a-ebfe4f30e71d","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 06 Nov 2019 04:31:32 -0800","resolved_at":null,"started_at":null,"startTime":"Wed, 06 Nov 2019 04:31:32 -0800","endTime":null,"updatedAt":"Wed, 06 Nov 2019 04:31:32 -0800","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/768d9296-5a2a-4d37-8f8a-ebfe4f30e71d","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2019-11-06T12:31:32.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/8696e49b-8d6e-40ae-8d30-1367ff7ab557","title":"LastPass - Issue with LastPass Identity","description":"[Resolved] On 10/30/2019, from 12:32 until 12:43 UTC, a subset of LastPass customers may have experienced transient errors and slowdowns with LastPass Identity. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize any future recurrences.","pubDate":"Wed, 30 Oct 2019 09:32:06 -0700","link":"https://status.lastpass.com/incidents/8696e49b-8d6e-40ae-8d30-1367ff7ab557","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 30 Oct 2019 09:32:06 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 30 Oct 2019 09:32:06 -0700","endTime":null,"updatedAt":"Wed, 30 Oct 2019 09:32:06 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/8696e49b-8d6e-40ae-8d30-1367ff7ab557","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"critical","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2019-10-30T16:32:06.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/4793ee31-fb7d-4b7f-80f5-79446d0ff889","title":"Connection Error (RESOLVED)","description":"[Resolved] The Network Operations Center resolved an issue with LastPass where some customers may have experienced intermittent errors when attempting to access LastPass.com from 4:50am - 5:12am ET.","pubDate":"Wed, 02 May 2018 05:41:51 -0700","link":"https://status.lastpass.com/incidents/4793ee31-fb7d-4b7f-80f5-79446d0ff889","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 02 May 2018 05:41:51 -0700","resolved_at":null,"started_at":null,"startTime":"Wed, 02 May 2018 05:41:51 -0700","endTime":null,"updatedAt":"Wed, 02 May 2018 05:41:51 -0700","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/4793ee31-fb7d-4b7f-80f5-79446d0ff889","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2018-05-02T12:41:51.000Z","_parsedEndTime":null},{"id":"https://status.lastpass.com/incidents/763fc379-cead-4fe2-b744-98896e48c31e","title":"Server Not Available Error","description":"[Resolved] The intermittent connectivity issue should now be resolved and operating normally. \r\n \r\n We will keep monitoring the affected components to ensure full service.\r\n \r\n Our apologies again for any inconvenience caused, and thank you all for your patience.","pubDate":"Wed, 21 Feb 2018 09:15:31 -0800","link":"https://status.lastpass.com/incidents/763fc379-cead-4fe2-b744-98896e48c31e","status":"unknown","impact":"none","isResolved":false,"created_at":"Wed, 21 Feb 2018 09:15:31 -0800","resolved_at":null,"started_at":null,"startTime":"Wed, 21 Feb 2018 09:15:31 -0800","endTime":null,"updatedAt":"Wed, 21 Feb 2018 09:15:31 -0800","incidentUpdates":[],"affectedComponents":[],"guid":"https://status.lastpass.com/incidents/763fc379-cead-4fe2-b744-98896e48c31e","originalData":{},"source":"api","vendor":"LastPass","healthScoreSeverity":"major","healthScoreSeveritySource":"text","vendorId":"lastpass","_parsedIsResolved":true,"_parsedStartTime":"2018-02-21T17:15:31.000Z","_parsedEndTime":null}],"unfilteredCount":64,"lastUpdated":"2026-07-11T23:24:44.278Z","wowDeltas":{"success":true,"windowDays":7,"vendorsTotal":105,"worse":[{"vendorId":"coinbase","delta":233,"currentCount":10,"previousCount":3,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"qualys","delta":125,"currentCount":9,"previousCount":4,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"abnormal","delta":100,"currentCount":1,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"bigid","delta":100,"currentCount":1,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"cursor","delta":100,"currentCount":4,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"fortinet","delta":100,"currentCount":4,"previousCount":2,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"island","delta":100,"currentCount":1,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"newrelic","delta":100,"currentCount":1,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"openai","delta":100,"currentCount":4,"previousCount":2,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"openrouter","delta":100,"currentCount":1,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"redhat","delta":100,"currentCount":2,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"snowflake","delta":100,"currentCount":2,"previousCount":1,"sustainedElevatedFlat":false,"ok":true}],"noChange":[{"vendorId":"airtable","delta":0,"currentCount":1,"previousCount":1,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"alertlogic","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"amazon","delta":0,"currentCount":1,"previousCount":1,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"appomni","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"aquasec","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"asana","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"bitbucket","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"box","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"builder","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"cockroachlabs","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"dropbox","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"duo","delta":0,"currentCount":0,"previousCount":0,"sustainedElevatedFlat":false,"ok":true}],"better":[{"vendorId":"1password","delta":-100,"currentCount":0,"previousCount":2,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"atlassian","delta":-100,"currentCount":0,"previousCount":1,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"broadcom","delta":-100,"currentCount":0,"previousCount":2,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"cisco","delta":-100,"currentCount":0,"previousCount":4,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"fastly","delta":-100,"currentCount":0,"previousCount":8,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"okta","delta":-100,"currentCount":0,"previousCount":2,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"paloalto","delta":-100,"currentCount":0,"previousCount":7,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"perplexity","delta":-100,"currentCount":0,"previousCount":2,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"solarwinds","delta":-100,"currentCount":0,"previousCount":1,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"stripe","delta":-100,"currentCount":0,"previousCount":2,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"tines","delta":-100,"currentCount":0,"previousCount":1,"sustainedElevatedFlat":false,"ok":true},{"vendorId":"digitalocean","delta":-100,"currentCount":0,"previousCount":6,"sustainedElevatedFlat":false,"ok":true}],"lastUpdated":"2026-07-11T21:48:06.198Z","fromCache":true}}