AWSOutage history and postmortems
Downtime, added up
AWS: 5h 19m weighted downtime in range, category median 39m.
12 incidents, 5d of incident time (3h 38m major or critical, 4d 21h partial) between Jun 27, 2026 and Sep 24, 2026.
Amazon Web Services, Inc. (AWS) is a subsidiary of Amazon that provides on-demand cloud computing platforms and APIs to individuals, companies, and governments, on a metered, pay-as-you-go basis.
Stated causes
16 incidents with no cause stated.
Postmortems
- DynamoDB DNS failure takes down US-EAST-1
Automation that manages critical DNS needs its own guard against writing an empty record, and dependent services need to recover from a stale state on their own.
- Internal network congestion disrupts US-EAST-1
Retry storms turn a small change into congestion; clients need backoff, and monitoring must not share the network it monitors.
- Mistyped command removes S3 index servers in US-EAST-1
Tools should refuse to remove capacity below a safe minimum, and the status page cannot depend on the system it reports on.
AWS incidents
32 on file
Questions
Is AWS down right now?
Check AWS's own status page at https://health.aws.amazon.com/health/status for the live state. This page shows AWS's incident history from that page; the most recent incident started 2026-09-21: "Increased Error Rates".
How often does AWS have outages?
AWS posted 12 incidents in the last 90 days and 30 in the last year, 1 of them major or critical in the last 90 days. The median incident lasted 2h 11m.
When was AWS's last major outage?
2026-07-16: "Increased 5xx Errors", lasting 3h 38m.
What usually causes AWS incidents?
Where AWS explained the cause, the most common was network (7 incidents). Most status updates do not name a cause.
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.