GitHub reported this critical-impact incident on its official status page on Sep 13, 2026, 09:16 UTC. It was resolved after 1h 29m.
Right now GitHub is operational. Live GitHub status →
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 cluster stores permission data read on nearly every authenticated request. The safeguard that was pacing the background job watched only one health signal — how far the database replicas were lagging — and that signal stayed low the whole time. It did not account for the load building on the primary i
Pull Requests is experiencing degraded performance. We are continuing to investigate.
We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor
We're seeing increased database replication delays on collab which is causing increased error rates in authorization endpoints and follow-on increased error rates across the system - we are investigating
Actions is experiencing degraded performance. We are continuing to investigate.
We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests
Overlapping incidents aren't necessarily related.
GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history