August 17 Outage and Future Challenges

GitHub stated that the 7-hour and 47-minute outage on August 17 disrupted core services including github.com, authentication, GitHub Actions, APIs, pull requests, issues, and Copilot. This was the second major incident following the Actions outage on August 6, occurring as critical infrastructure in the Central US data center failed to scale in response to a traffic surge.

The root cause of this outage was capacity shortage, not code or configuration changes. Monthly commit counts increased from 1.4 billion to 2.9 billion since April, placing increased load on the system, but GitHub emphasized that this does not justify the outage.

To improve reliability, GitHub added over 3 million CPU cores, 120PB of high-speed storage, and additional network capacity. Currently, Azure handles approximately 58% of the platform load and half of Git operations, a significant expansion from 12% in May. Additionally, GitHub plans to introduce an architecture where read capacity scales linearly with the number of readers to support large-scale monorepos.

Recognizing the limitations of operational practices, GitHub strengthened investments in availability, testing, rollouts, observability, and alerting systems. In particular, it immediately implemented measures applying retry limits and variable timeouts during inter-service interactions to prevent retry storms and cascading load.