AI Stresses Cloud Capacity
AI Development Strains GitHub, Forcing Microsoft to Use AWS for Capacity
Anonymous
Key Points
1
GitHub’s own reporting showed uptime far below its stated SLA: developer Mitchell Hashimoto tracked 90.21% uptime on the platform—well under GitHub’s 99.9% service-level agreement.
2
GitHub metrics underscore how quickly demand has shifted: COO Kyle Daigle said commits are on pace for 14 billion in 2026, up from about 1 billion in 2025. A separate report also says GitHub initially planned to scale capacity 10x, then raised the target to 30x after AI tool usage outpaced expectations by late 2025.
3
Microsoft confirmed it is seeking additional compute from third-party cloud providers while emphasizing that the surge in “agentic development” has tested its infrastructure—though a Microsoft spokesperson did not specify or confirm the AWS arrangement to the outlet.
4
The AI “agentic” workflow is described as changing GitHub traffic and stressing specific backend systems: Techzine reports AI agents now rapidly run through code, pull requests, and test cycles, increasing pressure on “databases, storage, search functions, and automation systems.” It also says Azure is already carrying substantial traffic and that repository replication is “nearly complete,” even as AWS is used temporarily.
5
Amazon’s Missouri AI infrastructure expansion includes detailed buildout targets: a planned 138 MW of carbon-free capacity, free-air cooling expected to limit water use to about 7% of the year, and collaboration with Arable Labs targeting about 100 million gallons of annual water savings—along with more than 400 full-time jobs and over $7 million in community investments.
Microsoft has quietly turned to rival Amazon Web Services to keep GitHub running after a surge in AI-driven coding pushed the platform into repeated outages. Independent developer Mitchell Hashimoto tracked GitHub's actual uptime at just 90.21% — far below the 99.9% the company promises in its service-level agreement, according to Windows Central.
GitHub COO Kyle Daigle said commits are on pace to hit 14 billion in 2026, up from about 1 billion in 2025. That 1,300% jump — driven by AI "agents" that write, test, and revise code automatically — has strained GitHub's infrastructure to the breaking point, forcing Microsoft to seek help from its biggest cloud rival.
AI Agents Trigger a 14-Billion-Commit Crisis
Traditional GitHub traffic was built around humans — occasional commits and pull requests. "Agentic" coding changes that entirely. AI tools now run hundreds of test cycles and thousands of code iterations in minutes. GitHub COO Kyle Daigle said this shift has "fundamentally changed the nature of repository traffic," according to Windows Central.
The pressure falls hardest on GitHub's backend: databases, storage, search, and automation systems, BizTech Weekly reported. Microsoft had already planned to scale capacity 10x. By late 2025, after AI tool usage blew past projections, it raised that target to 30x. Even that may not be enough to keep pace with the current demand.
Microsoft Turns to Amazon as Azure Migration Stalls
Microsoft bought GitHub for $7.5 billion in 2018 and had pledged to move it fully onto Azure by 2027. That plan is now in flux. Reports from multiple outlets say Microsoft secured temporary compute capacity from AWS around June 10, 2026 to stabilize the platform. A Microsoft spokesperson did not confirm the AWS arrangement directly, according to Windows Central.
Microsoft framed the move as a strategic "augmentation," not a failure. A spokesperson said repository replication to Azure is "nearly complete" and that the core problem is global capacity limits — not Azure-specific shortcomings. Still, BizTech Weekly noted the move signals a shift toward a broader multicloud approach to avoid future capacity crunches.
Developers Furious as Uptime Misses SLA by Nearly 10 Points
The numbers are hard to spin. Mitchell Hashimoto, former CTO of HashiCorp, tracked GitHub's uptime independently and found it sitting at 90.21% — nearly 10 percentage points below the 99.9% SLA GitHub advertises. That gap has sparked calls for service credits and a wider debate about whether a single centralized platform can survive the AI era, according to Windows Central.
The frustration is compounded by scale. GitHub is not a niche tool — it is the backbone of global software development. When it goes down, millions of developers and AI pipelines stop. The move to AWS is a pragmatic fix, but it also shows that even the world's largest cloud providers are struggling to keep up with the AI boom.
Amazon Builds Missouri Campus to Catch AI Overflow Demand
While Microsoft scrambles to stabilize GitHub, Amazon is racing to build more capacity. The company announced a multi-billion-dollar data center campus in Montgomery County, Missouri. The project will deliver 138 MW of carbon-free power and use free-air cooling to limit water consumption to about 7% of the year, according to Yahoo Finance.
Amazon is partnering with Arable Labs to cut water use by roughly 100 million gallons per year. The Missouri campus will also create more than 400 full-time jobs and bring over $7 million in community investment. The buildout signals that Amazon sees the AI capacity crunch — the same one squeezing GitHub — as a long-term business opportunity, Yahoo Finance reported.
Sentiment
Mostly PositiveNEGATIVENEUTRALPOSITIVE
Publishers
11
Articles
13
Reach
24
A
AnonymousAuthor
