GitHub’s latest outage took Copilot down with it, creating one of the most disruptive developer breakdowns we’ve seen in months — a fix is rolling out
GitHub experienced a significant outage beginning at approximately 9:40 AM ET, affecting thousands of developers worldwide and creating one of the most disruptive breakdowns in recent months. The incident impacted core platform functionality including API requests, pull requests, and webhooks, with error rates around 20% for both web experiences and API traffic according to GitHub’s official status page.
The outage extended to GitHub Copilot, the AI-powered code assistant relied on by millions of developers and companies globally, amplifying the impact across the development community. The simultaneous failure of both GitHub’s core services and Copilot resulted in widespread workflow disruptions, halting development efforts for countless organizations and teams dependent on these essential tools. Potential productivity losses from the incident were estimated in the millions of dollars.
The outage underscored the critical dependency the modern development ecosystem has on GitHub’s infrastructure. GitHub acknowledged the technical issues and immediately began rolling out fixes to restore full service functionality, prioritizing resolution of API errors, pull request handling, and Copilot availability to return developers to work.