
Agent-Scale Git Infrastructure: How GitHub Moved 99.99999% of Repositories to Azure and Adopted Per-Reference Quorums
Moving GitHub to the cloud sounds like a simple bandwidth problem, yet the busiest 0.00001% of repositories ran straight into network physics. With 1,000 miles and 25 ms of latency between on-prem data centers and Azure, a global repository lock turns parallel pushes from dozens of AI agents into a standstill traffic jam.
Switching Spokes to per-reference quorums and offloading reads to ephemeral replicas backed by Blob Storage sped up writes by 3–4x. Almost every object in Git is immutable, after all—only one tiny piece actually needs strict synchronization across servers.





