"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. In affected cases, notes GitHub, changes from previously merged pull requests and prior commits were inadvertently reverted by subsequent merges."
"AI is a factor, according to the source shack: 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."
"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."
GitHub has issued an apology for its recent availability and reliability issues, acknowledging repeated downtime that has led some developers to seek alternatives. Recent incidents include a Merge Queue bug that caused incorrect commits and an overloaded Elasticsearch cluster that disrupted search functionality. Uptime has dropped below 85 percent, with a downward trend noted since 2025. GitHub plans to increase capacity significantly and is focusing on improving availability, reducing unnecessary work, and isolating critical services to address these challenges.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]