This incident marks the platform's second significant service disruption in August, following an earlier failure on August 6.
The outage highlights the strain on GitHub’s infrastructure as activity surges, with monthly commits nearly doubling from 1.4 billion to 2.9 billion since April.
During the recovery process, some Copilot services remained down longer because client-side "retry loops"—where software repeatedly attempts to reconnect—created an additional surge of traffic.
This behavior forced engineering teams to mitigate the secondary load before they could safely restore full access to the global developer community.
To prevent future capacity failures, GitHub is accelerating its migration to Microsoft Azure, which now handles 58% of the platform’s total load compared to 12% in May.
The company has also added three million CPU cores and is implementing "retry budgets," a technical mechanism that limits how many times services can automatically reconnect to avoid cascading system pressure.
These architectural changes are designed to isolate critical systems and ensure the platform can scale to meet the increasing demands of large software projects.