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 32 min ago

Incidents with a published root cause

By month, last two years · Neon

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.

Neon
May 16, 2025
Databases could not start in AWS us-east-1
Customers in AWS us-east-1 could not create databases or wake suspended ones on 16 May and again on 19 May, about five and a half hours of impact in total; already-running databases were unaffected.
Root cause, as stated by Neon
Neon says that on 16 May a query plan change overloaded its control-plane database, so idle databases stopped suspending; pod counts rose past planned capacity and used up the IP addresses in two of the region's three subnets. On 19 May, reverting network settings changed during the first incident made IP allocation fail again, a phase Neon said it was still investigating.
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 us-central1. 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 32 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.