<div id="readability-page-1"><div id="body"> Microsoft's code hosting shack Github has published a lengthy mea culpa about its availability and reliability woes - one that includes the words &#34;we are sorry.&#34; Developers using the service have faced repeated downtime, and the apology comes days after Hashicorp co-founder Mitchell Hashimoto declared the platform is &#34;no longer a place for serious work&#34;, announcing plans to move his terminal emulator project, Ghostty, elsewhere. GitHub highlighted several recent incidents in its post. On April 23th, a Merge Queue bug caused merge groups containing more than one pull request to produce incorrect commits. &#34;In affected cases,&#34; notes GitHub, &#34;changes from previously merged pull requests and prior commits were inadvertently reverted by subsequent merges.&#34; Then on April 27th, parts of the user interface dependent on search stopped showing results after GitHub's Elasticsearch cluster became &#34;overloaded (likely due to a botnet attack).&#34; GitHub is still working on a root cause analysis. The problems are not new. In February, The Register noted that GitHub was struggling with availability. Uptime for the service, according to a reconstructed status page, dropped below 90 percent in 2025, and the trend has been downward. April's uptime is now below 85 percent. AI is a factor, according to the source shack: &#34;The main driver is a rapid change in how software is being built. Since the second half of December 2025, agentic development workflows have accelerated sharply.&#34; In between the handwringing, GitHub admits it had planned to up capacity by 10X and said it began work to do this in October 2025. However, by February this year, it became clear that 30 times as much capacity is required. GitHub has since scrambled to deal with the issues. &#34;Our priorities are clear: availability first, then capacity, then new features. We are reducing unnecessary work, improving caching, isolating critical services, removing single points of failure, and moving performance-sensitive paths into systems designed for these workloads.&#34; What about the migration to Azure? That is not the culprit. GitHub says the migration has actually helped, allowing it to &#34;stand up a lot more compute&#34; quickly. <ul> <li>IBM's AI coding 'partner' Bob hits general availability</li> <li>Microsoft's GitHub shifts to metered AI billing amid cost crisis</li> <li>Tokenmaxxing isn't an AI strategy</li> <li>Claude Opus 4.7 has turned into an overzealous query cop, devs complain</li> </ul> Yesterday, Hashimoto complained in a post on his website: &#34;For the past month I've kept a journal where I put an 'X' next to every date where a GitHub outage has negatively impacted my ability to work. Almost every day has an 'X'. On the day I am writing this post, I've been unable to do any PR review for ~2 hours because there is a GitHub Actions outage.&#34; GitHub's apology was penned by Chief Technology Officer, Vlad Fedorov, who closed with: &#34;We hear the pain you're experiencing. We read every email, social post, support ticket, and we take it all to heart.&#34; &#34;We're sorry.&#34; Restoring developer confidence to pre-crisis levels - when it was the go-to place for stashing code and collaborating on projects - will take more than words. ® </div></div>

ESTC

CLOU

GitHub has issued an apology regarding its recent availability and reliability issues, acknowledging repeated downtime that has led developers to question its viability for serious work. Notable incidents include a Merge Queue bug and an Elasticsearch overload. Uptime has dropped below 85% in April 2025, with GitHub admitting it underestimated the required capacity. The company is prioritizing improvements in availability and capacity while addressing the root causes of these outages. GitHub's CTO expressed empathy for developers' frustrations, emphasizing the need to restore confidence in the platform.

GitHub says sorry and vows to do better as uptime slips and devs complain