Amazon Web Services incident

Service impact: Increased Connectivity Issues and API Error Rates

Amazon Web Services experienced a major incident on March 2, 2026 affecting Service impact: Increased Connectivity Issues and API Error Rates (global) and Service impact: Increased Connectivity Issues and API Error Rates — global and 1 more component, lasting 50d 9h. The incident has been resolved; the full update timeline is below.

Started: Mar 02, 2026, 09:03 AM UTC
Resolved: Apr 21, 2026, 06:36 PM UTC
Duration: 50d 9h
Detected by Pingoru: Mar 02, 2026, 09:03 AM UTC

Affected components

Service impact: Increased Connectivity Issues and API Error Rates (global)Service impact: Increased Connectivity Issues and API Error Rates — globalAWS Status

Update timeline

monitoring Mar 02, 2026, 09:03 AM UTC

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.