Amazon Web Services

Cloud infrastructure · Official status page (opens in a new tab)

Counts cover incidents in this archive only. They are not a complete outage history or a reliability measure.

Failures in Amazon Web Services's systems

Incidents where the documented failure was in Amazon Web Services's own systems. Durations are measured to the end points the sources give.

  • Nov 15, 2026
    Amazon Web Services: Increased Connectivity issues in US-EAST-1 (N. Virginia)
    Unknown · Root cause unknown
    Stated cause

    The provider has not stated a cause in its status updates.

    Duration: 2 h 15 minto: Provider marked resolvedResolved
  • Oct 20, 2025
    AWS us-east-1 outage: an empty DNS record takes down DynamoDB and much of the region
    Amazon DynamoDBAmazon EC2Network Load Balancer+5
    Software defect · Root cause confirmed
    Stated cause

    A latent race condition in DynamoDB's automated DNS management left the regional endpoint dynamodb.us-east-1.amazonaws.com with an empty DNS record that the automation could not repair.

    Duration: 14 h 32 minto: All AWS services recoveredResolved
  • Dec 7, 2021
    AWS us-east-1 outage: automated scaling floods AWS's internal network
    EC2 APIsAWS Management ConsoleRoute 53 APIs+6
    Software defect · Root cause confirmed
    Stated cause

    An automated activity to scale capacity of an AWS service in the main network triggered unexpected behavior from many clients inside AWS's internal network. The surge overwhelmed the devices connecting the two networks, and a latent issue stopped clients from backing off as designed, so retries kept the network congested.

    Duration: 11 h 10 minto: Last service recovered (EventBridge)Resolved
  • Feb 28, 2017
    AWS S3 outage: a mistyped command removes too many servers in us-east-1
    Amazon S3S3 consoleEC2 new instance launches+3
    Human error · Root cause confirmed
    Stated cause

    While debugging the S3 billing system, an authorized team member ran a command from an established playbook to remove a small number of servers. One input was entered incorrectly, and a much larger set of servers was removed, including servers for the S3 index and placement subsystems.

    Duration: 4 h 17 minto: S3 operating normallyResolved
Showing 4 of 4 documented here

Contributed to other outages

Amazon Web Services's systems played a documented part in another provider's outage.

  • Jan 4, 2021
    Slack outage after the holidays: overloaded AWS network gateways
    Slack messaging and web tierSlack's internal provisioning serviceSlack's dashboards and alerting
    Failure at Slack · Network equipment · Root cause confirmed
    Stated cause

    An AWS Transit Gateway in Slack's network became overloaded as traffic jumped after the holidays and dropped packets. AWS told Slack that part of its networking infrastructure "had indeed become saturated and was dropping packets." Slack's autoscaling and instance provisioning then ran into limits that slowed recovery.

    Duration: Not computableResolved
Showing 1 of 1 documented here