Live / Incidents / GitHub Copilot
GitHub Copilot: Incident with several GitHub Services
GitHub Copilot · github.comImpact: criticalResolved2026-09-13 10:44 UTC
Public — what happened
Summary
On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications, Code Scanning, Git LFS, and new account signup. At peak, 8.8% of requests to create GitHub App installation access tokens failed. Token issuance for Actions workflows was also affected, impacting approximately 4% of workflows during the incident time frame. Creating issues through the web interface failed for about 96% of attempts, and signup failures were above 90%. <br /> <br />The cause was an internal data-cleanup job that began writing to a shared database cluster at 07:33 UTC. That cl
Timeline
- Started — 2026-09-13 09:16 UTC
- Last update — 2026-09-13 10:44 UTC
- Resolved — 2026-09-13 10:44 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 →