AWS outage history and postmortems

Cloud and hosting · Seattle, US · 12 incidents in 90 days · 99.75% implied uptime · last 3d ago

Incidents

32 on file

Started	Incident	Impact	Root cause	Duration
Sep 2123:26 UTC	Increased Error Rates	minor	Not disclosed	58m
Sep 321:49 UTC	Increased API Error Rates	minor	Not disclosed	2h 18m
Aug 2102:02 UTC	Increased Error Rates	minor	Not disclosed	38m
Aug 1915:15 UTC	Increased Error Rates	minor	Not disclosed	3h 32m
Aug 1503:42 UTC	Increased Packet loss	minor	Network	3d
Jul 3117:33 UTC	Elevated Packet Loss	minor	Config change	1h 21m
Jul 2411:40 UTC	Connectivity Issues	minor	Network	1h 21m
Jul 1708:33 UTC	Inaccurate Estimated Billing Data	minor	Config change	29h 24m
Jul 1608:44 UTC	Increased 5xx Errors	major	Network	3h 38m
Jul 1523:11 UTC	Elevated connectivity issues with a single Avalability zone	minor	Network	2h 13m
Jul 612:45 UTC	Increased Launch Template API Error Rates	minor	Not disclosed	2h 8m
Jun 3021:02 UTC	Increased Error Rates and Latencies	minor	Config change	51m
Jun 1301:26 UTC	Fable 5 and Mythos 5 Access	minor	Not disclosed	2d 16h
Jun 604:24 UTC	Internet Connectivity Issues	minor	Not disclosed	0m
May 2223:38 UTC	Increased API Error Rates	minor	Not disclosed	35m
May 800:25 UTC	Increased Error Rate and Latency	minor	Power	26h 39m
Apr 2711:27 UTC	Increased Connectivity Issues	minor	Not disclosed	39m
Mar 719:53 UTC	Increased Error Rates	major	Storage	1h 11m
Mar 205:56 UTC	Region Availability	critical	Network	Ongoing
Mar 112:51 UTC	Region Availability	critical	Network	Ongoing
Feb 2518:14 UTC	Intermittent missing or delayed EC2 instance and status check metrics	minor	Not disclosed	2h 37m
Feb 2100:38 UTC	AWS Direct Connect Connectivity Issues	minor	Not disclosed	1h 35m
Feb 1021:15 UTC	Change Propagation Delays	minor	Not disclosed	7h 4m
Feb 718:30 UTC	Network Connectivity	minor	Not disclosed	0m
Jan 2817:14 UTC	Elevated latencies for network change propagation	minor	Config change	2h 8m
Oct 2822:36 UTC	Increased Error Rates and Latencies	minor	Not disclosed	7h 20m
Oct 2007:11 UTC	Increased Error Rates and Latencies	critical	DNS	15h 42m
Oct 2006:48 UTC	DynamoDB DNS failure takes down US-EAST-1	critical	DNS	14h 32m
Sep 2703:25 UTC	Increased Error Rates and Latencies	minor	Not disclosed	33m
Sep 2521:56 UTC	SQS Increased API Error Rates	minor	Not disclosed	7h 28m
Dec 715:30 UTC	Internal network congestion disrupts US-EAST-1	critical	Network	7h 10m
Feb 2817:37 UTC	Mistyped command removes S3 index servers in US-EAST-1	critical	Operator	4h 17m

About AWS

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.

The last year, day by day

No incident Minor Major CriticalDeeper colour: longer outage

Downtime, added up

Cloud and hosting median

5h 19m

AWS: 5h 19m weighted downtime in range, category median 39m.

12 incidents, 1 major or critical, 5d of incident time (3h 38m major or critical, 4d 21h partial), longest 3d, implied uptime 99.75%, between Jun 28, 2026 and Sep 25, 2026.

Stated causes

16 incidents with no cause stated.

Postmortems

Started	Incident	Impact	Root cause	Duration
Oct 2006:48 UTC	DynamoDB DNS failure takes down US-EAST-1	critical	DNS	14h 32m
Dec 715:30 UTC	Internal network congestion disrupts US-EAST-1	critical	Network	7h 10m
Feb 2817:37 UTC	Mistyped command removes S3 index servers in US-EAST-1	critical	Operator	4h 17m

Across fru.dev:Company profile Acquisitions Compliance Free tiers Paydays Regions Regions Changefeed SLAs TechConf Uptime

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.

Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.