Microsoft borrows AWS capacity to keep GitHub online as AI agents overwhelm the platform
Microsoft confirmed on June 16, 2026 that it is routing GitHub traffic through Amazon Web Services after a surge in AI coding agent activity pushed the platform past the reliability thresholds its enterprise customers expect.
The crisis by the numbers
GitHub COO Kyle Daigle confirmed in April that the platform was processing 275 million commits per week, on pace for 14 billion in 2026 — up from 1 billion in 2025.
Other staggering numbers:
- GitHub Actions: 2.1 billion compute minutes per week (vs. 500 million in 2023)
- AI-opened PRs: from 4 million in September 2025 to 17 million in March 2026 — a 325 percent increase
- Availability: dropped to ~88.4 percent in June, well below the 99.9 percent enterprise SLA
- Incidents: nine service-degrading incidents in May 2026 alone
Community reaction
Mitchell Hashimoto, co-founder of HashiCorp, captured developer frustration: GitHub was no longer a place for serious work if it just blocks you out for hours per day, every day.
GitHub own CTO Vlad Fedorov had acknowledged in February and March that the platform had breached its three-nines availability commitment, and disclosed in October 2025 that the company had begun executing a plan to increase capacity 10 times over.
The irony
When Microsoft acquired GitHub for $7.5 billion in 2018, the strategic logic was that GitHub would become a natural on-ramp to Azure. Eight years later, GitHub AI demand curve exceeded Azure ability to absorb it, and Microsoft biggest cloud competitor is keeping its developer platform online.
Lesson: AI adoption is outpacing infrastructure planning — even at the scale of the world second-largest cloud provider.