Following a series of dozens of large-scale outages on GitHub, Microsoft is seeking assistance from its rival AWS, citing the immense strain on its infrastructure due to AI-driven growth.
It has been revealed that Microsoft is planning to use AWS to increase GitHub's computing power in response to storage capacity issues.
Microsoft turns to AWS for GitHub capacity amid Azure lawsuit
Microsoft turns to Amazon as AI-driven growth at GitHub strains its infrastructure
https://www.thehansindia.com/technology/tech-news/microsoft-turns-to-amazon-as-ai-driven-growth-at-github-strains-its-infrastructure-1086915
Microsoft forced to turn to AWS to boost GitHub cloud capacity following AI demand surge | TechRadar
https://www.techradar.com/pro/microsoft-forced-to-turn-to-aws-to-boost-github-cloud-capacity-following-ai-demand-surge
In 2018, Microsoft acquired GitHub, a platform for developers to store code, manage software projects, and collaborate. Prior to the acquisition, GitHub was primarily operated in Microsoft's own data centers.
However, since its acquisition by Microsoft, GitHub has been gradually migrating to Microsoft's cloud computing service, Azure, with a complete migration planned by 2027.
GitHub, however, is suffering from storage capacity issues.
Kyle Daigle, GitHub's Chief Operating Officer, posted on X in April 2026, 'GitHub activity is surging. We've gone from 1 billion commits (code changes) in 2025 to 275 million commits per week now. If this continues, we'll have a total of 14 billion commits in 2026.' He added, 'So we need to put in more CPU, scale the service, and strengthen GitHub's core functionality. And we're working incredibly hard to do that.' This revealed that development on GitHub was booming and putting a strain on computing resources.
Yup, platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.)
— Kyle Daigle (@kdaigle) April 3, 2026
GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now… https://t.co/iGsM2j1efO
Furthermore, GitHub has faced reliability issues with its service, having experienced dozens of major outages since the beginning of 2026. You can check how many outages GitHub has experienced since the beginning of 2026 on 'Red Squares'.
'Red Squares' visualizes GitHub's downtime over the past year in a 'grass' format - GIGAZINE
Sources have revealed that Microsoft is seeking cooperation from Amazon Web Services (AWS), a rival of Azure, to resolve this issue. According to reports, GitHub's increased use of AWS is due to the increased development activity driven by the proliferation of AI coding tools.
A Microsoft spokesperson commented on the report, stating, 'The phenomenal surge in AI agent development that began at the end of 2025 is testing the limits of our infrastructure,' acknowledging the surge in GitHub usage due to the proliferation of AI agents. While Microsoft acknowledged using multiple cloud providers, it declined to comment on Amazon's involvement.
Microsoft continues to focus on expanding its infrastructure, with capital expenditures expected to reach $190 billion (approximately 30 trillion yen) in 2026. The majority of this investment is planned to be used to increase data center capacity.
Furthermore, investors dissatisfied with the various AI-related problems Microsoft is facing have filed lawsuits against it, claiming that 'Microsoft's flagship proprietary AI model has significantly underperformed its competitors in numerous benchmark tests' and 'Microsoft has failed to convert a substantial percentage of its commercial Microsoft 365 users to paid Copilot subscriptions, and its Copilot products are losing market share to competitors, a trend that continues to worsen.'
Microsoft faces down sueball, capacity problems in series of challenges
https://www.theregister.com/systems/2026/06/16/microsoft-faces-down-sueball-capacity-problems-in-series-of-challenges/5256175
Related Posts:
in AI, Software, Web Service, Posted by logu_ii