Centralized Git was always going to break under agent load. The protocol that Linus shipped in 2005 was designed for a handful of humans running git push from a coffee shop — not a swarm of coding agents each running shallow-clone → edit → push in a tight loop, thousands of times an hour, against the same repository. By 2026, that constraint is showing up as GitHub rate-limit emails, flaking CI, and "the agent pool is throttled" Slack messages. The fix has been talked about for years — mirror traffic, push to CDN, fan out the read side — but nobody had shipped it as a product with public numbers.
Entire just shipped the first credible answer. The preview of their distributed Git network is live under waitlist, with active mirrors in the US, EU, and Australia, and the numbers from the initial test run are the first real evidence that the agent era has a Git backend it can grow into: ~570,000 clones/hour, 586 pushes/second (~2.1M/hour), and a sustained ~470 clone+push ops/sec on a single repository at ~50–60 ms p50 latency. The Git backend itself is going open source. If you've been waiting for the infrastructure story to catch up to the agent story, this is it.
The problem, in one line
