GitHub puts nearly all repositories in Azure amid agent traffic
Original title: The bridge to agent-scale Git infrastructure
Per-reference quorums target the last 0.00001% of repos; tests saw 3–4x write throughput.
GitHub says 99.99999% of its Git repositories now also live in Azure after a migration driven by exponential Git traffic, data-center power limits, and agentic growth. The busiest remainder is blocked by about 25ms cross-region round trips under a repository-wide write quorum. GitHub is moving serialization to individual references so those repos can move, and plans read scaling via Azure Blob Storage.
Unconfirmed: The post describes the per-reference quorum and independent read scaling as the planned bridge, not as fully finished for the last repositories.
- The first repository copy landed in Azure Central US in August 2025.
- Most repositories have two of five replicas in Azure, serving about half of Git traffic.
- Internal tests saw 3–4x higher throughput on writes to different references.
- Reads are described as 100 to 1,000 per write.
- Products
- AzureAzure Blob StorageGit
- Organizations
- GitHub
From the original article
7 min read at github.blog
We moved a copy of 99. 99999% of GitHub’s repositories to Azure. Here’s how per-reference quorums will bring over the rest, and how object storage lets reads scale independently.
By Klaster_1 · github.blog
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.