GoKawiilGitHub moves most Git repository replicas to Azure amid capacity crunch
GitHub reports that nearly all repositories on its platform now have copies split between its own data centers and Microsoft Azure, with the first repository replica landing in Azure's Central US region in August 2025. The company says most repositories currently keep two of their five replicas in Azure, which now serves roughly half of all Git traffic, while a small set of the busiest repositories remain constrained by a 25ms network round trip.
GoKawiil's interpretation of the reporting above, not reported fact.
GitHub says the migration was forced by exponential traffic growth tied to agentic workloads, combined with power capacity limits at its data centers and supply chain constraints, suggesting the company had limited runway to redesign its architecture before acting. By moving data first and planning to redesign the underlying storage system afterward, GitHub appears to be sequencing a high-risk infrastructure overhaul to avoid disrupting a service it treats as critical to nearly all platform operations.
- Most GitHub repositories now have replicas split between GitHub's own data centers and Azure.
- The first repository replica moved to Azure's Central US region in August 2025, with Azure now handling about half of Git traffic.
- A small subset of the busiest repositories remain limited by a 25ms round-trip latency issue.
Source: github.blog — Eleanor White, 2026-10-21
Published there as: “The bridge to agent-scale Git infrastructure”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.