GitHub Shifts 52.75% of Read Traffic to Azure Central US After 9-Hour Actions Outage
Updated
Updated · github.blog · Aug 12
GitHub Shifts 52.75% of Read Traffic to Azure Central US After 9-Hour Actions Outage
3 articles · Updated · github.blog · Aug 12
Summary
52.75% of GitHub monolith read traffic ran in Azure Central US on July 28, the first sustained move above 50%, while Git traffic there rose to 47% from 43% in June.
GitHub said it is accelerating the Azure migration after an Aug. 6 GitHub Actions outage exposed how launch service still running in its own data centers worsened capacity limits and delayed recovery.
29% of repositories now have a second replica in Central US, authentication has begun moving off GitHub’s oldest shared database, and dedicated services are offloading more than 1 million queries per second.
The company is using new stability validation checks for each major traffic expansion and shifting reliability metrics toward customer workflows such as pull requests, not just infrastructure health.
GitHub is targeting 70% of read traffic and 30% of write traffic in Central US this quarter, with a second Azure region and full exit of dotcom production traffic from its data centers by end-2026.