GitHub’s June Was Its Best Month Ever. The Infrastructure Almost Broke.

GitHub Chief Technology Officer Vladimir Fedorov told employees on Wednesday, June 24, 2026 that June had been “by far” the platform’s best month ever. The driver was a June 1 switch to usage-based pricing for Copilot, the AI coding tool Microsoft owns alongside the developer platform. Microsoft declined to comment on the internal remarks.

The same demand surge that produced the record is straining GitHub’s infrastructure hard enough that Microsoft has turned to its biggest cloud rival for help. Per a separate Business Insider report, Microsoft is adding computing capacity from Amazon Web Services after dozens of major outages this year. Fedorov declined to share specific revenue or usage figures, and he would not confirm any pricing plans.

What GitHub Changed on June 1

On June 1, 2026, GitHub moved Copilot from a flat monthly subscription per user to usage-based billing, charging customers for how much they actually use the tool instead of a fixed fee for a fixed allotment of requests. The shift lined GitHub up with its coding-tool rivals, Cursor, OpenAI’s Codex, and Anthropic’s Claude Code, all of which already bill by consumption. “June was by far our best month ever,” Fedorov said at the internal meeting, according to GitHub’s June record under usage-based Copilot pricing. Microsoft did not challenge the characterization in a comment to the outlet.

The pricing reset was framed internally as an alignment with how the rest of the AI coding market now charges. Cursor had already made consumption pricing the norm for power users, while OpenAI’s Codex and Anthropic’s Claude Code followed the same path. GitHub’s prior model, a flat-rate seat with a fixed request quota, looked increasingly out of step with how heavy users actually work, especially once coding agents started burning through quotas around the clock.

On prices going up, Fedorov said he personally does not think GitHub needs to raise prices much. He stopped short of confirming any definitive pricing plans.

The Numbers Behind “Best Month Ever”

The activity surge has metrics to back it up. GitHub Chief Operating Officer Kyle Daigle posted the latest figures on X in April 2026, captured in full on the commit figures Kyle Daigle posted in April. The numbers describe a different kind of growth than the platform has seen before.

At that pace, 2026 would be the biggest year in the platform’s history by a wide margin. Daigle hedged the projection himself, noting the growth will not actually stay linear. The shift from a flat subscription model to usage-based billing removed the per-seat friction that had capped how much a single account could push through the system. The new ceiling is whatever a coding agent, or a hundred of them, can hit in a week.

GitHub Actions has scaled faster than the commit count. The service is one of the largest CI and automation platforms in the world, running jobs for repos of every size. Agent workflows have a habit of triggering Actions runs at a rate human developers rarely matched.

Fedorov confirmed in a separate blog post that agentic development workflows have accelerated sharply since late December 2025, pushing repository creation, pull request activity, API usage, and large-repository workloads to record highs simultaneously. GitHub had originally planned for a 10x capacity increase back in October 2025. By February 2026, internal estimates had grown to 30x today’s scale. The numbers behind the record, in raw form, sit in the list below.

• 1 billion commits across all of 2025
• 275 million commits per week, April 2026
• 14 billion projected commits in 2026 if growth stays linear
• 500 million GitHub Actions minutes per week, 2023
• 2.1 billion GitHub Actions minutes in a single week, April 2026

The Infrastructure Strain Behind the Record

The same demand spike that produced the record broke things repeatedly, and GitHub experienced dozens of major outages in 2026. The pattern hit hardest in April, when two specific incidents landed within four days. On April 23, a merge queue bug silently reverted previously merged code across 658 repositories and 2,092 pull requests. Four days later, on April 27, a botnet attack overwhelmed GitHub’s Elasticsearch cluster and knocked out search-dependent UI across pull requests, issues, and projects. Neither incident involved data loss, though both hit developers where it hurts most, their ability to ship work.

April’s uptime slipped below 85 percent, far below the platform’s stated 99.9 percent SLA. The outages that drew the most attention were the April 23 merge queue bug and the April 27 Elasticsearch attack. GitHub acknowledged the strain publicly after the latter incident.

The capacity crunch forced Microsoft into a posture it had publicly resisted. Microsoft is now adding computing capacity via Amazon Web Services, two people familiar with the plans told Business Insider, in the report on Microsoft turning to AWS for GitHub capacity. Microsoft had originally planned to move GitHub entirely to its own Azure cloud by 2027. The plan assumed growth on a normal software-development cadence. Agent demand grew on a different curve.

The incredible spike in agentic development that began late last year has tested our infrastructure’s limits.

A Microsoft spokesperson acknowledged the strain in unusually direct terms. The spokesperson said Microsoft is “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,” according to Business Insider. The “multi-cloud strategy” framing is the first time Microsoft has publicly treated Azure alone as insufficient for GitHub. Pricing has not yet entered the public framing.

The dollar number attached to this surge is large. Microsoft recently projected $190 billion in capital expenditures for the 2026 calendar year, mostly for data center capacity.

From October to June, Demand Doubled on Itself

The arc from October to June is the story of how agent-driven demand outran GitHub’s infrastructure planning. By February 2026, the internal capacity ask had multiplied by three from the October baseline. The dates and the scale of each escalation sit in the list below.

The popular developer personality ThePrimeagen put the moment in plain language in an X post that has since gone viral: “I have to put respect on github for handling the amount of shit code that has been added over the last 3 months. literally 10s of billions of lines of code that will never see the light of a CPU.” Daigle’s reply, on his own feed, became its own headline: “As a fine purveyor of hand-crafted shit code for many years, I’m not gonna weigh in on that.” Underneath the joke sits a more pointed observation ThePrimeagen made in the same thread: “GitHub has been around since April 10, 2008. Agents came out yesterday. GitHub was in fact NOT designed for agents.”

OpenClaw creator Peter Steinberger, whose open-source AI assistant has become a leading example of multi-agent development, has publicly said he keeps hitting GitHub API quota limits, a frustration tied to the same human-centric design. His mobile app launch the same week drew complaints of its own, per OpenClaw’s mobile app launch and its local-first limits. HashiCorp cofounder Mitchell Hashimoto logged nearly daily outage disruptions in a personal journal for a month. He then announced he was leaving GitHub entirely. GitHub user number 1,299, on the platform since February 2008, his departure became the most visible flashpoint of the outage streak, with Fedorov issuing a public apology and Daigle acknowledging the team has been “keeping heads down on infra” while usage climbs.

1. October 2025: GitHub plans for a 10x capacity increase.
2. December 2025: Agentic development workflows begin accelerating sharply.
3. February 2026: Internal estimates grow to a 30x capacity ask.
4. April 23, 2026: A merge queue bug reverts merged code across 658 repositories and 2,092 pull requests.
5. April 27, 2026: A botnet attack overwhelms GitHub’s Elasticsearch cluster.
6. June 1, 2026: Copilot switches to usage-based pricing.
7. June 24, 2026: Fedorov tells staff June was the platform’s best month ever.

The Competition That Forced GitHub’s Hand

The June 1 pivot was not optional. Cursor, OpenAI’s Codex, and Anthropic’s Claude Code had all moved to consumption pricing before GitHub did, and each had been eating into GitHub’s lead among AI-native developers. GitHub had an early lead because of its popularity as a place to store and manage code, but that lead did not extend automatically to the AI coding era. In an internal Microsoft meeting late last year, an executive spoke about the need to overhaul GitHub to compete with these tools, according to audio reviewed by Business Insider.

GitHub has been inside Microsoft since the 2018 acquisition, but the product had not been rebuilt for the agent era. The June 1 pricing change was the first public signal that the rebuild was reaching customers. Fedorov’s “best month ever” remark was the second. The Copilot app’s shift toward managing multiple agents in parallel, per Copilot’s app turning developers into AI fleet managers, puts the same pressure on the consumer product surface. Whether the third signal is a price hike, a multi-cloud expansion beyond Azure plus AWS, or a deeper platform rewrite for autonomous agents, that sits in the next quarter’s filings and announcements.

Frequently Asked Questions

When did GitHub change Copilot to usage-based pricing?

GitHub changed Copilot’s billing on June 1, 2026. The new model bills customers based on how much they use the tool, replacing the prior flat-rate per user fee for a fixed allotment of requests.

Who are GitHub Copilot’s main AI coding competitors?

Business Insider named three: Cursor, OpenAI’s Codex, and Anthropic’s Claude Code. All three already used usage-based pricing before GitHub switched.

Why is GitHub having outages in 2026?

Microsoft attributed the outages to an “incredible spike in agentic development that began late last year.” GitHub experienced dozens of major outages in 2026, including an April 23 merge queue bug that reverted merged code for 658 repositories and 2,092 pull requests, and an April 27 botnet attack that overwhelmed GitHub’s Elasticsearch cluster.

Why is Microsoft turning to AWS for GitHub capacity?

Microsoft had planned to move GitHub entirely to its own Azure cloud by 2027. AI demand grew faster than Azure’s near-term capacity, and Microsoft is now adding computing capacity through Amazon Web Services as part of what the company calls a “multi-cloud strategy.”

Is GitHub going to raise Copilot prices?

Fedorov said he personally does not think GitHub needs to raise prices much based on the usage spike, but stopped short of confirming any definitive pricing plans. Microsoft has not commented on specific Copilot pricing moves.