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

Incidents listed

By month, last two years · Buildkite

Peak 0 · December 2024

Incidents listed: 0; Last two years
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.

Buildkite
Sep 9, 2026
Two windows of widespread errors
In two windows totalling about an hour, all customers saw errors and latency in the web interface, APIs and agent communication, with delayed job dispatch.
Root cause, as stated by Buildkite
An autoscaling feedback loop following a migration to a new container platform opened more connections than a shared Redis cluster could accept.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)
Buildkite
Oct 20, 2025
Latency and errors during AWS us-east-1 outage
The Buildkite web interface and APIs were slow with elevated errors, and job dispatch and notifications were delayed, by over an hour for the worst-affected customers, across roughly seven and a half hours.
Root cause, as stated by Buildkite
Buildkite says EC2 launch failures during the AWS us-east-1 outage stopped its autoscaling from adding capacity, so it could not scale up for US business-hours traffic and used up all available compute.
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-east1. 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 6 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.