GitHub saw 7.4B commits in September, adding 4M CPU cores and 160 PB of storage to keep up
GitHub now sees 7.4 billion commits a month, driven largely by AI agents, and is adding 4 million CPU cores and rearchitecting its platform to keep up.
by Frederic Lardinois · The New StackGitHub is seeing unprecedented demand and is updating its core infrastructure to keep pace.
In August, GitHub said it was seeing 2.9 billion commits per month, up from 1.4 billion in April. At its GitHub Universe conference on Wednesday, the company announced that it is now seeing 7.4 billion commits per month. To put that into perspective, developers pushed 65 million monthly commits to the platform in 2024.
That kind of growth is a great problem to have, but the company’s outages have become something of a recurring theme. The reason is rapid usage growth, driven mostly by “agentic demand,” as the company puts it.
4 million more CPU cores
In August, GitHub CTO Vlad Fedorov announced that the platform had added 3 million CPU cores — mostly on Azure — to support this growth. Now, GitHub says it has added 4 million CPU cores, plus 160 petabytes of high-speed storage and more compute power for GitHub Actions so far this year
The company also added 50 Tb/s of network capacity to keep all of this data flowing.
A new GitHub architecture is coming
GitHub also used this announcement to reiterate its commitment to rearchitecting its platform to separate compute and storage. It first talked about this earlier this month. At that time, the company noted that its internal benchmarks show that this new architecture can deliver up to 35x higher write throughput, for example.
“Agents are changing the volume and shape of software development. Adding capacity matters, but capacity alone won’t get us there. We’ve also had to change the architecture,” Jay Parikh, the EVP for Core AI at Microsoft, writes in the announcement.
Separating compute and storage isn’t exactly radical in 2026, but it shows GitHub was trying to scale on a legacy foundation. Moving to Azure and its services was essentially the only option, especially as the company’s own data center was out of capacity.