FuriaHubGitHub’s August 17 outage lasted 7 hours and 47 minutes
GitHub said a Central US capacity failure on August 17 took down github.com, authentication, Actions, APIs, pull requests, issues, and Copilot for 7 hours and 47 minutes. CTO Vladimir Fedorov wrote that neither that incident nor the August 6 Actions failure was caused by a code or configuration change.
On August 20, 2026, GitHub published a postmortem of the August 17 outage. The company said a capacity failure in its Central US data center lasted 7 hours and 47 minutes and disrupted github.com, authentication, Actions, APIs, pull requests, issues, and Copilot.
What we know
- CTO Vladimir Fedorov wrote that neither the August 6 Actions failure nor the August 17 outage was caused by a code or configuration change; both were capacity failures.
- Monthly commits grew from 1.4 billion in April to 2.9 billion.
- Azure now serves about 58% of platform load, up from 12% in May, and half of all Git operations.
- GitHub said it has added more than 3 million CPU cores and 120 petabytes of high-speed storage as part of its reliability work.
Takeaways
- The August 17 incident was a Central US capacity failure, not a bad deploy.
- Commit volume has roughly doubled since April.
- GitHub is shifting more load to Azure while adding on-prem cores and storage.
Source: GitHub
