Fetching from the wire…
Top 5 · 2026-06-18 · source-backed
Microsoft confirmed on June 16 that it's routing GitHub burst workloads, specifically GitHub Actions runners and Codespaces, onto Amazon's cloud after agentic coding pushed the platform below its own three-nines availability target. Read that again. Microsoft, which owns GitHub and Azure, is paying its biggest cloud rival to absorb overflow it can't handle. (TechTimes)
The numbers explain why. Agent-generated pull requests went from 4 million a month in September 2025 to 17 million a month by March 2026. That's a 325% jump in roughly six months. GitHub now processes around 275 million commits a week, on pace for 14 billion in 2026. May alone had nine service-degrading incidents serious enough to breach enterprise SLAs.
Here's what I think actually happened. We spent two years treating "the agent opened a PR" as a clever demo. Nobody modeled what happens when every developer's fleet of subagents is opening PRs in parallel, triggering CI on every push, spinning up Codespaces, and re-running the whole thing on every self-correction loop. Agents don't commit like humans. They commit like a load test that never stops. The same auto-retry and mid-stream recovery features that make agents resilient (more on those below) also mean a flaky run gets retried instead of abandoned, multiplying the traffic.
For builders the read is concrete. Stop assuming CI is free and infinite. Pin your CI runner versions and cache aggressively so a degraded GitHub Actions backend doesn't silently re-pull your whole dependency tree. Expect throttling. Build your pipelines to tolerate a queued or delayed run instead of treating a slow webhook as a failure. If your product depends on GitHub Actions as a backend (a surprising number of indie SaaS tools do), you now have a dependency with a publicly admitted capacity problem and a migration timeline that even Azure can't meet on its own. Design for degraded, not for the happy path. The platform layer under all of us just admitted it's overloaded.
Each link below shares sources, entities, or timing with this story.
Amazon released AWS / Shared entities / Same source / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Amazon released AWS); both cover AWS, GitHub, Microsoft, SLAs; cite the same source (TechTimes).
Microsoft released Azure / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Microsoft released Azure); both cover Agent, Azure, GitHub, Microsoft; overlapping topics (agent, azure, commit).
Amazon released AWS / Shared entities / What happened next
Linked by a graph relationship (Amazon released AWS); both cover AWS, Azure, GitHub, March; picks up the AWS thread on 2026-08-15.
Amazon released AWS / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Amazon released AWS); both cover AWS, Azure, GitHub, GitHub Actions; overlapping topics (action, commit, dependency).
Amazon supports Claude Code / Shared entities / What happened next
Linked by a graph relationship (Amazon supports Claude Code); both cover Agent, AWS, GitHub, Microsoft; picks up the Agent thread on 2026-08-08.
Amazon released Trainium / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Amazon released Trainium); both cover Amazon, AWS, Azure, Microsoft; overlapping topics (azure, cloud, microsoft).
Microsoft released Azure / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Microsoft released Azure); both cover Agent, Azure, Microsoft; overlapping topics (agent, azure, microsoft, million, month).
Microsoft released Copilot / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft released Copilot); both cover Codespaces, GitHub, GitHub Actions; overlapping topics (action, admitted, agent, commit, month).