GitHub blames AI-driven traffic surge for seven-hour outage

GitHub has attributed a recent outage lasting more than seven hours to capacity failures rather than code or configuration errors. The developer platform reported that a critical infrastructure component in its Central US data centre failed to scale with a new peak in traffic, rendering several services inaccessible on Monday.

The surge in demand is significant, with GitHub noting that monthly commits have grown from 1.4 billion to 2.9 billion since April. This doubling of volume in four months represents a substantial increase in the number of changes being made to projects hosted on the platform.

The platform stated that this growth explains the pressure on its systems, although it acknowledged that the volume does not excuse the outages. The uptick in usage aligns with the rising amount of code produced by artificial intelligence tools, a trend that is placing increasing strain on digital infrastructure.

To mitigate future risks, GitHub is implementing technical adjustments to how it handles simultaneous activity. The company is reviewing CPU and memory alerts to identify server components likely to fail during high-traffic periods. Additionally, it is applying consistent retry limits, retry budgets, and variable timeouts across service-to-service interactions to prevent retry storms and cascading load.

While these measures address immediate infrastructure handling, they do not fully account for the underlying trend driving the traffic spike. With both Anthropic and OpenAI continuing to develop their AI coding tools, the pressure on GitHub’s systems is expected to persist.

As the default home for professional and hobbyist software projects, GitHub remains positioned to continue feeling the impact of AI-driven code generation. The platform’s response highlights the growing challenge of scaling infrastructure to accommodate the rapid expansion of automated development workflows.