The library. Every incident, structured.
A growing archive of public postmortems, broken down into a consistent shape: what broke, why it cascaded, and what to take from it. New incidents added regularly.
28+
incidents
11+
years
13
organizations
/
sort
4 results · filtered
GitHub
id
incident
org
date
duration
severity
tags
FM-016
The Search Layer That Slowed GitHubA concentrated wave of anonymous scraping traffic saturated the load-balancing tier in front of GitHub Search, causing timeouts across issues, pull requests, repositories, Actions, packages, and Dependabot alerts.
GitHub
2026-04-27
6h 31m
SEV-2
searchscrapingload-balancing
FM-029
The Silent Merge Queue Corruption That Hit 658 GitHub ReposA half-gated feature flag let an unreleased merge-base path escape into squash merge groups. Over a 4h38m impact window, GitHub's merge queue produced valid-looking commits that silently reverted prior work across 658 repositories and 2,092 pull requests.
GitHub
2026-04-23
4h38m
SEV-1
merge-queuefeature-flagsquash-merge
FM-027
The Runner Cache Bug That Queued Ubuntu CI JobsA backend cache misconfiguration after failover caused duplicate GitHub Actions job assignments, reducing Ubuntu-24 runner capacity for public repos.
GitHub
2025-05-28
5h
SEV-2
cischedulerfailover
FM-002
43 Seconds of Split-Brain at GitHubA 43-second network partition between GitHub's East and West Coast sites tripped automatic failover. By the time the partition healed, both coasts had taken writes and reconciling the split took most of a day.
GitHub
2018-10-21
24h 11m
SEV-1
databasemysqlreplication