What’s gone wrong at GitHub?
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
GitHub's reliability has deteriorated sharply, with 257 incidents tracked between May 2025 and April 2026, including 48 major outages. GitHub Actions alone suffered 57 outages in that period. The root cause, per GitHub's CTO, is the explosive growth of agentic AI workflows demanding 30x the platform's designed capacity. High-profile users like Mitchell Hashimoto (Ghostty) and the Zig project have migrated away. Compounding the scaling crisis are engineering failures like an incomplete feature flag that silently reverted thousands of merged pull requests. Microsoft's absorption of GitHub into its CoreAI org and commercial pressure around Copilot are seen as contributing factors. GitHub has declared an 'availability first' mandate, but community patience is running thin as comparable platforms like GitLab and npm handle the same AI-driven growth without comparable disruptions.
Table of contents
Your inbox, upgraded.An exodusMore like thisIs AI precipitating GitHub’s reliability crisis?What a better GitHub would look likeThe bigger picture16 Comments
Sort: