GitHub infrastructure overwhelmed by AI agent traffic; Microsoft turns to AWS for elastic compute

ME AI messages, according to two informed sources, although Microsoft plans to fully migrate GitHub to Azure by 2027, frequent outages and capacity crises have prompted Microsoft to bring in AWS for elastic support. According to official disclosures from GitHub, the platform is expected to reach 14 billion commits in 2026, compared to just 1 billion commits in 2025. GitHub’s Chief Technology Officer, Vlad Fedorov, revealed that in October 2025, the team designed a 10x scaling plan, but following a surge in agent development workflows by the end of December 2025, they were forced in February 2026 to increase the designed capacity to 30x. Infrastructure overload has directly threatened the stability of the developer ecosystem. In May 2026, GitHub experienced nine service degradation incidents. In April of the same year, HashiCorp co-founder Mitchell Hashimoto announced plans to move the Ghostty project off the platform, stating that GitHub’s frequent outages no longer support serious development work. Despite Microsoft’s projected capital expenditures of $190 billion for 2026, Chief Financial Officer Amy Hood warned that compute supply-demand bottlenecks will persist until the end of 2026. Regarding the multi-cloud hosting strategy, a Microsoft spokesperson responded that the surge in agent development since late 2025 has put extreme pressure on GitHub’s infrastructure, and while the company is accelerating its migration to Azure, it will ensure elasticity and scale through a multi-cloud strategy. Procuring compute resources across clouds is not unique in today’s tight compute environment; Google has also recently entered into a multi-year contract with SpaceX to purchase computing resources at a monthly cost of $920 million. (Source: BlockBeats)