Amazon Web Services incident

Service disruption: Increased Error Rates

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

Affected components

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

Update timeline

  1. monitoring Mar 02, 2026, 06:46 AM UTC

    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.

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