Amazon Web Services incident

Service degradation: Increased Error Rates

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

Affected components

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

Update timeline

  1. monitoring Mar 01, 2026, 03:09 PM UTC

    We wanted to provide some additional information on the isolated power issue. At this time, most AWS Services have weighted away from the affected Availability Zone (mec1-az2) and are seeing recovery for their affected operations and workflows. For EC2 Instances, EBS Volumes, and other resources that are impacted in the affected Zone, we will have a longer tail of recovery. At this time, power has not yet been restored to the affected AZ. For now, we recommend continuing to retry any failed API requests. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources by launching replacement resources in one of the unaffected zones, or an alternate region. As of this time, recovery is still several hours away. We will provide an update by 8:30 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