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

Incidents listed

By month, last two years · PlanetScale

Peak 3 · January 2026

Incidents listed: 15; Last two years
Official write-ups: 0; Linked from the incident
Major outages: 1; As graded by each company
Services: 1; 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.

PlanetScale
Oct 20, 2025
Control plane outage and network partitions in us-east-1
Customers could not create or resize database branches and the dashboard was intermittently unavailable; later, network partitions in AWS us-east-1 caused query failures for some databases there, with the incident resolved after about thirteen hours.
Root cause, as stated by PlanetScale
PlanetScale says a DNS misconfiguration at one of its service providers and the Amazon DynamoDB outage in AWS us-east-1 took out upstream dependencies of its control plane; later it could not launch new EC2 instances there and partial network partitions cut some database servers off across availability zones.
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

PlanetScale · Problems with Vitess connectivity and credential changes
Partial outage · Oct 26, 2026 · 1 h 38 min
PlanetScale · AWS us-east-1 connectivity failures
Partial outage · Oct 9, 2026 · 26 min
PlanetScale · Connectivity issues with Vitess databases in GCP
Partial outage · Sep 5, 2026 · 14 min
PlanetScale · Dashboard and API 500 errors for postgres databases
Partial outage · Sep 2, 2026 · 10 min
PlanetScale · Insights metrics underreporting
Partial outage · Jul 24, 2026 · 3 h 0 min
PlanetScale · Connectivity issues in us-east-1
Partial outage · Jul 18, 2026 · 33 min
PlanetScale · API and dashboard errors
Partial outage · Jul 17, 2026 · 28 min
PlanetScale · There is an incident in PlanetScale GCP us-central1 region impacting Postgres database availability. We are actively investigating and will update as soon as we have more information.
Partial outage · May 14, 2026 · 32 min
PlanetScale · us-east-1 connection errors
Partial outage · Mar 11, 2026 · 15 min
PlanetScale · Vitess branch creation unavailable
Partial outage · Feb 24, 2026 · 1 h 34 min
PlanetScale · Vitess database availability issues in GCP northamerica-northeast1
Partial outage · Feb 18, 2026 · 43 min
PlanetScale · Query insights outage
Major outage · Jan 31, 2026 · 2 h 19 min
PlanetScale · API availability issues
Partial outage · Jan 9, 2026 · 17 min
PlanetScale · Errors with branch creation for GCP databases
Partial outage · Jan 6, 2026 · 1 h 14 min
PlanetScale · API and dashboard: 500 errors
Partial outage · Nov 17, 2025

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 40 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.