Amazon Web Services incident

Service impact: Increased Error Rates

Major Resolved View vendor source →
Started
Mar 01, 2026, 01:19 PM UTC
Resolved
Apr 21, 2026, 06:36 PM UTC
Duration
51d 5h
Detected by Pingoru
Mar 01, 2026, 01:19 PM UTC

Affected components

Service impact: Increased Error Rates (global)Service impact: Increased Error Rates — globalAWS Status — global

Update timeline

  1. monitoring Mar 01, 2026, 01:19 PM UTC

    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.

Looking to track Amazon Web Services downtime and outages?

Pingoru polls Amazon Web Services's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Amazon Web Services reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Amazon Web Services alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Amazon Web Services for free

5 free monitors · No credit card required