Outages and root causes.

Two years of public outages, and what each company said caused them. Every entry links to the company's own write-up; nothing here is our speculation.

Status pages re-read 3 min ago

Incidents with a published root cause

By month, last two years · Amazon Web Services

Peak 0 · December 2024

Incidents listed: 0; With a published RCA
Official write-ups: 0; Linked from the incident
Major outages: 0; As graded by each company
Services: 0; With at least one entry

Notable outages, summarised

Read from each company's published analysis and summarised in our own words. Follow the link for the full account.

Amazon Web Services
Oct 20, 2025
DynamoDB DNS failure cascades across US-EAST-1
DynamoDB's regional endpoint in N. Virginia stopped resolving, which then broke EC2 launches, Network Load Balancers, Lambda and many other AWS services for customers in the region. Impact came in three phases over roughly 14.5 hours (started late on 19 October Pacific time).
Root cause, as stated by Amazon Web Services
A latent race condition in DynamoDB's automated DNS management let a stale plan overwrite a newer one and then be cleaned up, leaving the regional endpoint with an empty DNS record.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)
Amazon Web Services
Jul 30, 2024
Kinesis Data Streams degradation in US-EAST-1
An internal Kinesis cell used by other AWS services degraded, causing errors and delays in CloudWatch Logs, Data Firehose, ECS, Lambda, Redshift, Glue and S3 event delivery in N. Virginia for close to seven hours.
Root cause, as stated by Amazon Web Services
The cell management system mishandled a cell with a very large number of low-throughput shards, wrongly marking healthy hosts unhealthy and triggering shard redistribution that overloaded a connection-provisioning component.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

From the status pages

With a published RCA Partial and major outages Both

Showing incidents whose vendor named northamerica-northeast1. Incidents with no stated region are not included, though they may have affected it too.

Nothing matches these filters.

Who publishes root causes

Write-ups posted on status pages, last two years

Public information only

Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.

Sources

Official status pages: incident titles, severity, times and the link to each published root-cause analysis, exactly as each company posted them
Company engineering blogs and incident reports: the basis for the notable-outage summaries, each linked from its card

How fresh it is

Incidents and RCA links: re-read from every status page about once an hour; last run 3 min ago
Notable-outage summaries: written by hand and last checked against their sources on Nov 10, 2026

Titles, severity and times are as published on each company's status page. "Published RCA" means the company posted a postmortem on that incident's official page; we link to it and do not reproduce it. Many companies publish root causes on a blog instead, or not at all, so the absence of a link is not evidence that no analysis exists. Severity grading differs between companies and is not comparable across them. This is not a complete record of every outage.

statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.