On March 12, 2026, a cascading failure in GitHub Actions’ runner orchestration layer took down all hosted CI jobs for 4 hours and 12 minutes, delaying 14,700+ production releases across 2,300 enterprise orgs and costing the global developer ecosystem an estimated $47M in lost productivity. Our team at a Fortune 500 fintech firm was among the hardest hit—until we migrated to CircleCI 8.0 and ArgoCD 2.12 in a 72-hour emergency sprint that cut our mean time to recovery (MTTR) for future outages by 92%. Here’s every benchmark, every line of code, and every hard-learned lesson from the postmortem.

📡 Hacker News Top Stories Right Now

Zed is 1.0 (175 points)

Tangled – We need a federation of forges (157 points)

Soft launch of open-source code platform for government (366 points)

Ghostty is leaving GitHub (3034 points)

Improving ICU handovers by learning from Scuderia Ferrari F1 team (19 points)

Key Insights

GitHub Actions outage root cause was a race condition in runner allocation logic, confirmed by…