GitHub blames 8-hour outage on autoscaling fail and VS Code retry storm
- ID
- 15567
- Status
- summarized
- Published
- 19 Aug 2026, 7:40 PM
- Fetched
- 19 Aug 2026, 8:37 PM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/saas/2026/08/19/github-blames-8-hour-outage-on-autoscaling-fail-and-vs-code-retry-storm/5289547
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 7.5
- Created
- 19 Aug 2026, 8:39 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
GitHub traced a near 8-hour outage (Aug 17, 13:28–21:15 UTC) to saturated load balancers in its Central US facility after an Istio sidecar hit its concurrency limit and a misconfigured autoscaling policy failed to respond. A latent VS Code retry bug amplified traffic ~10x against the Copilot Token Service, which took until 21:02 UTC to recover—long after Issues, PRs, APIs, and Actions came back.
Why it matters
If you ship CI/CD or AI-assisted workflows on GitHub Actions or Copilot, this incident shows a single internal endpoint + client retry loop can take down your pipeline for hours. Consider caching dependencies locally, maintaining a fallback CI provider, and reviewing your own autoscaling policies to ensure sidecar/agent concurrency limits—not just host metrics—are monitored.
Discussion angle
How many of us have a Plan B for a multi-hour GitHub outage—local git mirrors, alternate CI, or at least a runbook—or are we fully single-vendor dependent on GitHub + Copilot?