Amazon Web Services incident

Service disruption: Increased Error Rates

Major Resolved View vendor source →
Started
Mar 02, 2026, 12:26 AM UTC
Resolved
Apr 21, 2026, 06:36 PM UTC
Duration
50d 18h
Detected by Pingoru
Mar 02, 2026, 12:26 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, 12:26 AM UTC

    We are seeing significant signs of recovery for AssociateAddress requests, and continue to work toward fully mitigating this issue. This combined with the earlier recovery of the AllocateAddress API means customers can now successfully create and associate new network addresses in the unaffected AZs. Other AWS Services are also now observing sustained improvement as a result of the EC2 Networking APIs recovery. We are now focusing on implementing a change that will allow customers to Disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. We expect this specific mitigation to take another hour to complete. We do not have an ETA for power restoration at this time. For customers that can, we recommend using alternate Availability Zones or other AWS Regions where applicable. We will provide another update by 6:30 PM, 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