GitHub's 7-hour 47-minute global outage caused by capacity shortage

Summary

On August 17, 2026, GitHub experienced a global outage lasting 7 hours and 47 minutes due to an automatic scaling failure that couldn't handle a recorded traffic surge, which combined with a retry loop from client tools like VS Code.

Why it matters

The incident highlighted the fragility of centralized DevOps platforms under rapid growth, affecting millions of developers worldwide and exposing bottlenecks in capacity planning. It also underscores the scaling challenges when migrating legacy infrastructure to cloud services like Azure.

Highlights

• Traffic doubled since April, straining critical data center components.
• The client-side retry loop increased load during recovery, delaying service restoration.
• GitHub responded by adding 3 million CPU cores and 120 petabytes of high-speed storage.

Critical take

GitHub claims the outage wasn't caused by code changes, but reliance on a single automatic scaling mechanism indicates insufficient redundancy and testing for extreme traffic scenarios.