Inside GitHub’s Seven-Hour Outage: How a Hidden Bottleneck Cascaded Into a Global Slowdown
On August 17, developers around the world watched pull requests stall, sign-ins fail, and Copilot suggestions time out — not because anyone shipped broken code, but because a piece of infrastructure quietly ran out of room. The incident lasted 7 hours and 47 minutes, and by the time GitHub’s status page finally turned green, it had touched authentication, Actions, APIs, issues, pull requests, and its AI coding assistant. For a platform that hosts the daily work of millions of engineers, that is not a minor hiccup. It is a reminder that “the cloud” is really a chain of interdependent machinery, and chains break at their weakest link.





