Breaking: GitHub Warns of Capacity Strain After Back-to-Back Outages
GitHub has acknowledged two major availability incidents in recent weeks, attributing the failures to unprecedented demand from AI-powered development tools. The company says the outages are “unacceptable” and outlines an urgent plan to scale infrastructure.
“These incidents are not acceptable, and we are sorry for the impact they had on you,” said a GitHub spokesperson in a statement. “We are sharing details on what happened and what we’re doing to improve reliability.”
The platform, used by over 100 million developers, is reeling from a surge in automated workflows since December 2025. “Agentic development” — where AI agents create code, submit pull requests, and run tests — has accelerated sharply, driving exponential growth across repository creation, API usage, and large-repo workloads.
Background: The Scaling Challenge
GitHub initially planned a 10x capacity increase starting October 2025. But by February 2026, internal projections showed a 30x capacity requirement was needed to meet future demand. The driver: a rapid shift in how software is built, fueled by generative AI.
“This exponential growth does not stress one system at a time,” a GitHub engineering lead explained. “A single pull request can touch Git storage, mergeability checks, Actions, search, notifications, permissions, webhooks, APIs, caches, and databases. At high scale, small inefficiencies compound into cascading failures.”
The interconnected nature of GitHub’s distributed systems means that queues deepen, cache misses become database load, indexes fall behind, and retries amplify traffic. One slow dependency can affect multiple product experiences simultaneously.
What This Means: Priorities Shift to Availability Over Features
GitHub’s leadership has reset priorities: availability first, then capacity, then new features. The company is reducing unnecessary work, improving caching, isolating critical services, and moving performance-sensitive code into systems designed for these workloads.
“This is distributed systems work: reducing hidden coupling, limiting blast radius, and making GitHub degrade gracefully when one subsystem is under pressure,” said a senior infrastructure engineer. “We’re making progress quickly, but these incidents show there’s still work to do.”
Short-term fixes included moving webhooks out of MySQL, redesigning user session caches, and rewriting authentication flows to slash database load. GitHub also accelerated its migration to Azure to scale compute capacity.
Next steps involve isolating critical services like Git and GitHub Actions from other workloads, minimizing single points of failure, and migrating performance-sensitive code from Ruby monoliths to Go-based microservices. The company is also pursuing a multi-cloud strategy to reduce dependency on any single provider.
For developers relying on GitHub for continuous integration, automated testing, and deployment, the message is clear: expect further volatility until upgrades are complete. GitHub promises transparent communication on progress.