Key takeaways
- GitHub says it added 4 million CPU cores, 160 PB of high-speed storage and 50 Tb/s of network capacity so far in 2026.
- It is building a new Git architecture that decouples storage from compute, with no dates given.
- GitHub expects to finish its migration to a multi-region Azure deployment early next year.
GitHub says it has added 4 million CPU cores, 160 petabytes of high-speed storage and 50 terabits per second of network capacity so far this year, as it rebuilds its platform for the traffic AI coding agents create. The numbers come from a GitHub Universe post by Jay Parikh published on October 28, 2026.
The post is GitHub's most direct statement yet that agent-driven traffic is changing how it has to build. It says the platform has seen "incredible levels of traffic" and has to stay fast and reliable at that scale.
What GitHub says it has added
GitHub lists three additions "so far this year":
- 4 million CPU cores
- 160 PB of high-speed storage
- 50 Tb/s of network capacity
The post does not say how many commits, pull requests or agent sessions drove the buildout. Press coverage of the event reports a figure of 7.4 billion commits in September, but we could not find that number in GitHub's own post, so we do not rely on it.
A new Git architecture and a move to multi-region Azure
Capacity is half of the plan. GitHub says it is working on a new Git architecture built on three principles: simplify the primitives, minimize coordination, and decouple storage from compute. The post gives no implementation details or dates for the Git work.
It also says GitHub is moving to a multi-region deployment in Azure while continuing to serve developers, and expects to finish the migration early next year.
Why it matters for developers
GitHub is where most AI coding tools send their work, from Copilot's cloud agents to third-party agents that open pull requests. When agent traffic grows, it competes with everyone else's pushes, pulls and CI runs. The buildout is GitHub's answer to that, and its reliability over the next few months is the thing to watch.
GitHub's status page showed a separate incident on October 29, 2026: a disruption to Copilot Cloud services, with failures and latency in the agent sessions service, including creating and listing sessions. The status page marked it as ongoing when we checked.
What we don't know yet
GitHub has not published reliability figures for the year, the share of traffic that comes from agents, or a date for the new Git architecture. We will update this article when it does.
