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 2 min ago
Incidents with a published root cause
By month, last two years · Clerk
Peak 0 · December 2024
- Total: 0
- December 2024: 0
- January 2025: 0
- February 2025: 0
- March 2025: 0
- April 2025: 0
- May 2025: 0
- June 2025: 0
- July 2025: 0
- August 2025: 0
- September 2025: 0
- October 2025: 0
- November 2025: 0
- December 2025: 0
- January 2026: 0
- February 2026: 0
- March 2026: 0
- April 2026: 0
- May 2026: 0
- June 2026: 0
- July 2026: 0
- August 2026: 0
- September 2026: 0
- October 2026: 0
- November 2026: 0
- 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.
- Clerk
Mar 10, 2026
API outage from database lock contention
Clerk's APIs returned errors and rejected requests for about 26 minutes; most session token requests also failed for roughly the first quarter of an hour, until Clerk switched on a fallback mode that restored sessions.
Root cause, as stated by Clerk
A failed live migration of the virtual machine hosting Clerk's managed database caused a spike in disk latency and lock contention.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)
- Clerk
Feb 19, 2026
API outage from database slowdown
Most requests to Clerk were rejected for about 90 minutes; a failover restored existing sessions partway through, but sign-ins and account management stayed down until the database recovered.
Root cause, as stated by Clerk
An automatic statistics refresh in Postgres caused the planner to switch to an inefficient query plan that consumed nearly all database resources.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)
- Clerk
Jun 26, 2025
All Clerk services down
All Clerk services were unavailable to all customers for 45 minutes.
Root cause, as stated by Clerk
Clerk's compute containers on its cloud provider entered a restart loop, which Clerk attributes to a flaw in the provider's zonal redundancy that prevented failover to healthy capacity.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)
From the status pages
Showing incidents whose vendor named asia-southeast1. 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 2 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.