Amazon Web Services incident

Service disruption: Increased Error Rates

Major Resolved View vendor source →
Started
Mar 02, 2026, 02:22 PM UTC
Resolved
Apr 21, 2026, 06:36 PM UTC
Duration
50d 4h
Detected by Pingoru
Mar 02, 2026, 02:22 PM UTC

Affected components

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

Update timeline

  1. monitoring Mar 02, 2026, 02:22 PM UTC

    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. We 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.

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