'We let you down': GitHub pledges to scale up before developers give up
- ID
- 16469
- Status
- summarized
- Published
- 21 Aug 2026, 9:15 PM
- Fetched
- 21 Aug 2026, 11:39 PM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/devops/2026/08/21/we-let-you-down-github-pledges-to-scale-up-before-developers-give-up/5291031
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 7.5
- Created
- 21 Aug 2026, 11:39 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
GitHub's CTO Vladimir Fedorov acknowledged a 7-hour-47-minute outage on August 17 that disrupted Actions, pull requests, issues, Copilot, and APIs worldwide—the second major outage that month after an August 6 Actions failure. GitHub now handles 2.9 billion monthly commits, 24 million new repositories, and 130 million merged PRs, but its infrastructure hasn't scaled to keep up, with Microsoft Azure carrying ~58% of platform load. Fedorov pledged a linear read-scaling architecture rollout starting with the largest monorepos, plus retry-limit tightening and system isolation, but admitted neither outage was caused by a code or config change—meaning the failure modes were already latent.
Why it matters
If your CI/CD pipeline runs on GitHub Actions, these outages directly blocked shipping for nearly 8 hours, and the CTO's admission that failure modes were latent (not introduced by deployment) means more outages are likely before the architecture overhaul lands. Evaluate whether your team needs a fallback CI provider or cached dependency mirrors now, rather than waiting for the next incident. The detail that Azure handles only 58% of load means the migration is incomplete and reliability will remain uneven in the interim.
Discussion angle
What's your team's actual cost of a full-day GitHub outage, and is it worth setting up a secondary CI runner or mirror now given that GitHub's scaling fix is months away?