GitHub's Reliability Crisis Deepens as Creator Mitchell Hashimoto Exits Amidst Outages

GitHub, widely regarded as the most critical platform in software engineering, is grappling with a severe reliability crisis. Third-party monitoring reports reveal a significant decline in uptime, dipping below 90% in 2025 and an abysmal 86% in April 2026, starkly contrasting GitHub’s official status page which claims over 99%. The past week has been particularly tumultuous: on April 23rd, the platform’s Merge Queue inexplicably unmerged 292 pull requests across 658 repositories, effectively losing committed code. This was followed on April 27th by a botnet attack on GitHub’s Elastic Search subsystem, rendering search dysfunctional for hours. The crisis escalated on April 28th, with GitHub’s CTO issuing an apology for ongoing reliability issues, concurrently with the disclosure of a critical remote code execution vulnerability where git push operations could execute code on GitHub servers.

The growing developer frustration culminated in legendary developer Mitchell Hashimoto’s public departure. A long-time GitHub user (since 2008) and creator of tools like Vagrant and Terraform, Hashimoto announced on April 28th that he is migrating his 50,000-star open-source project, Ghosty, off the platform. Expressing his exasperation, Hashimoto stated, “I want to ship software, and it doesn’t want me to ship software,” citing persistent outages that have consistently blocked his work. The underlying cause for GitHub’s instability appears to stem from the “AI coding era” and a surge in “agentic development workflows,” as admitted by GitHub’s CTO. These AI agents are reportedly “hammering GitHub like it’s a free buffet,” transforming the platform into a host for automated processes rather than just human developers. While Microsoft, GitHub’s owner, is expected to address these challenges, alternatives like GitLab, Codeberg, and SourceHut are poised to benefit from developers seeking more stable and reliable code hosting solutions.