DEV TOOLS Signal 384
GitHub says monthly commits doubled to 2.9 billion, blaming capacity failure for outage
↗
GitHub's recent outage was caused by capacity failures as monthly commits grew from 1.4 billion to 2.9 billion since April.
For engineers relying on GitHub, the outage shows that infrastructure must scale with AI-driven code generation. GitHub is adding retry limits and variable timeouts to prevent cascading load, but the underlying traffic growth from AI coding tools is likely to continue.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Monthly commits on GitHub grew from 1.4 billion to 2.9 billion since April, more than doubling in four months.
The outage occurred because a critical infrastructure component in the Central US data center failed to scale with the new traffic peak.
GitHub is applying consistent retry limits, retry budgets, and variable timeouts across service-to-service interactions to prevent retry storms.
THE CLUSTER