GitHub Details August 17 Outage and Steps to Prevent Future Downtime

Overview

GitHub experienced a major service disruption on August 17 that lasted 7 hours and 47 minutes, affecting developers worldwide. The outage impacted core services including github.com, authentication, GitHub Actions, APIs, pull requests, issues, and Copilot.

Incident Details

The company stated the outage began when traffic reached a new peak and a critical infrastructure component in its Central US data center failed to scale accordingly. This capacity pressure spread across systems, causing authentication failures and disrupting multiple services.

Recovery Efforts

Teams rerouted traffic, isolated affected infrastructure, and restored services in stages. While most GitHub services recovered earlier in the day, some Copilot services took longer due to client-side retry loops that increased traffic during recovery.

Root Cause

Neither the August 17 outage nor a prior incident on August 6 was caused by code or configuration changes. Both were capacity failures. GitHub noted that monthly commits grew from 1.4 billion in April to 2.9 billion by August, contributing to system pressure.

Reliability Improvements

GitHub has added over 3 million CPU cores, 120 petabytes of high-speed storage, and significant network capacity. Azure now handles roughly 58% of GitHub’s platform load and half of all Git operations, up from 12% in May.

Ongoing Work

The company is isolating critical systems, removing shared dependencies, implementing consistent retry limits, and improving observability and alerting. A new architecture designed to scale read capacity linearly is planned for rollout beginning with the largest monorepos.

Leadership Context

Vladimir Fedorov, GitHub’s Chief Technology Officer, previously led engineering teams at Meta and co-founded UserClouds. He holds degrees in Computer Science from Caltech and serves on the board of Codepath.org.

What Readers Can Verify

Full technical details and a timeline are available in GitHub’s official post: https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/