Amazon Web Services incident

Service impact: Increased connectivity issues and API Error Rates

Resolved after 50 days 11 hours, 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, on March 2, 2026.

monitoring Mar 02, 2026, 07:09 AM UTC

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.

Started
Mar 02, 2026, 07:09 AM UTC
Resolved
Apr 21, 2026, 06:36 PM UTC
Duration
50d 11h
Detected by Pingoru
Mar 02, 2026, 07:09 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

  1. monitoring Mar 02, 2026, 07:09 AM UTC

    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.

Your product runs on more than Amazon Web Services

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →