Microsoft is temporarily supplementing GitHub’s cloud capacity with Amazon Web Services (AWS) to address a surge in AI-driven usage that has overwhelmed the platform’s infrastructure, according to two sources familiar with the plans. The move represents a rare collaboration between Microsoft’s Azure cloud and its largest competitor, AWS, as the tech giant accelerates a migration of GitHub to its own infrastructure while grappling with unprecedented demand. GitHub, acquired by Microsoft in 2018, has faced repeated outages in 2026 as AI coding tools—such as Cursor and Anthropic’s Claude Code—have driven a 14-fold increase in developer activity, according to internal Microsoft projections.
GitHub’s “commits”—records of code changes that serve as a proxy for development activity—are on pace to reach 14 billion this year, up from 1 billion in 2025, GitHub’s Chief Operating Officer, Kyle Daigle, wrote on X in April. The platform, which hosts over 100 million developers, has become a critical hub for AI-driven software development, but its infrastructure has struggled to keep pace. Microsoft’s decision to rely on AWS, even partially, underscores the urgency of the situation, as the company has faced delays in expanding its own data centers to meet demand.
A Microsoft spokesperson confirmed GitHub is exploring a “multi-cloud strategy” but declined to comment on whether AWS is involved. “The incredible spike in agentic development that began late last year has tested our infrastructure’s limits,” the spokesperson said. “To meet this demand, we are both accelerating our move to Azure and continuing to explore a multi-cloud strategy to ensure we have the future capacity, compute elasticity, and horizontal scale required to support continued growth.”
Amazon, which does not comment on individual clients, emphasized its commitment to providing “global infrastructure that performs reliably, securely, and efficiently at scale.” The company’s AWS division has become a dominant force in cloud computing, with a 32% market share in 2026, according to Gartner’s latest report. Microsoft’s Azure, while the second-largest cloud provider, has faced challenges in scaling its infrastructure quickly enough to meet the surging demand for AI-driven services.
Why Is Microsoft Relying on AWS for GitHub?
The decision to use AWS is driven by two key factors: the unprecedented growth in AI-driven development and delays in Microsoft’s own data center expansion. GitHub’s outages in 2026—including multiple incidents where the platform was inaccessible for hours—have frustrated developers and raised concerns about its reliability. Mitchell Hashimoto, co-founder of HashiCorp, recently wrote on X that GitHub was “no longer a place for serious work if it just blocks you out for hours per day, every day.”
Microsoft’s capital expenditures for 2026 are projected to reach $190 billion, with a significant portion allocated to expanding data center capacity. However, many of these projects have faced delays, forcing the company to seek alternative solutions. The reliance on AWS is not an isolated incident; other tech giants, including Google and SpaceX, have also turned to external providers to meet AI compute demands. Earlier this month, Google announced a $920 million monthly deal with SpaceX for AI compute capacity, while its own cloud division has partnered with Anthropic to supply AI infrastructure.
The surge in GitHub’s activity is tied to the rise of AI coding assistants, which automate much of the software development process. These tools generate code snippets, debug errors, and even write entire functions, leading to a dramatic increase in the volume of code being uploaded, reviewed, and stored on the platform. According to Statista, global cloud computing spending is expected to exceed $1.3 trillion by 2027, with AI-driven workloads accounting for nearly 40% of that growth.
How Does This Affect Developers and Competitors?
For developers, the short-term impact of GitHub’s outages has been significant. Many rely on the platform for version control, collaboration, and code hosting, and prolonged downtime can disrupt workflows. While Microsoft’s use of AWS may improve reliability in the near term, the long-term strategy remains focused on migrating GitHub entirely to Azure by 2027. However, the current capacity crunch has forced a temporary detour.
Competitors in the cloud computing space are watching Microsoft’s move closely. AWS has long been the leader in cloud infrastructure, and this partnership—however temporary—could be seen as a validation of its capabilities. Meanwhile, Microsoft’s Azure team is under pressure to accelerate its migration of GitHub services to ensure the platform can handle future demand without relying on external providers.
GitHub’s challenges also highlight the broader pressures facing cloud providers as AI adoption accelerates. Companies like Google and Meta have already announced plans to invest billions in AI-specific data centers, recognizing that traditional infrastructure is insufficient for the demands of large language models and generative AI tools. Microsoft’s situation reflects the broader industry trend: even the largest tech firms are struggling to keep up with the pace of AI-driven growth.
What Happens Next for GitHub and Microsoft?
Microsoft has not provided a timeline for when GitHub’s reliance on AWS will end, but the company’s long-term goal remains clear: a full transition to Azure. The spokesperson emphasized that the multi-cloud strategy is part of a broader effort to ensure “compute elasticity and horizontal scale” for GitHub’s growing user base. However, the decision to use AWS—even temporarily—raises questions about whether Microsoft’s internal infrastructure can keep pace with the demands of AI-driven development.
Developers and industry observers will be closely monitoring GitHub’s stability in the coming months. If outages persist, it could further erode trust in the platform, particularly as competitors like Cursor and Claude Code gain traction. Microsoft’s ability to resolve these issues will not only determine GitHub’s future but also send a signal to the broader tech industry about the challenges of scaling infrastructure for AI.
For now, the focus remains on ensuring GitHub remains operational. As Microsoft continues to invest in Azure and explore additional cloud partnerships, the company’s ability to balance short-term fixes with long-term strategy will be critical. The next major checkpoint will be Microsoft’s Q3 2026 earnings report, where the company is expected to provide updates on its cloud infrastructure investments and GitHub’s migration progress.
Have insights or tips on GitHub’s capacity challenges? Share them with us securely via email at [email protected] or through our secure submission form. Your contributions help us keep our readers informed.