Live / Incidents / GitHub Copilot
GitHub Copilot: Incident with GitHub.com
GitHub Copilot · github.comImpact: criticalResolved2026-08-17 21:15 UTC
Public — what happened
Summary
GitHub Copilot reported a critical incident on August 17, 2026, in which GitHub.com saw raised error rates and slowness affecting Issues, Pull Requests, APIs, Actions and Copilot, along with sign-in features such as SAML/OIDC, SCIM and Team Sync. The company said problems ran from 13:28 to 21:15 UTC, with web and API errors peaking near 20% and archive and raw file downloads near 50%. GitHub said the trigger was overloaded network load balancers in its Central US datacenter during a traffic peak, made worse by a scaling misconfiguration and aggressive retries, including a retry bug in VS Code that multiplied Copilot sign-in traffic about tenfold. Most services were back by 16:36 UTC, Actions by about 18:03, and the Copilot Token Service by 21:02, and the company listed follow-up steps on scaling, retry limits and monitoring.
Timeline
- Started — 2026-08-17 13:40 UTC
- Last update — 2026-08-17 21:15 UTC
- Resolved — 2026-08-17 21:15 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GitHub Copilot against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GitHub Copilot: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GitHub Copilot report →