Incident with several GitHub Services

Timeline

1. 09:16 UTC GitHub status page · Reported Incident with several GitHub Services
2. 09:16 UTC GitHub status page · Investigating We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests
3. 09:25 UTC GitHub status page · Investigating Actions is experiencing degraded performance. We are continuing to investigate.
4. 09:36 UTC GitHub status page · Investigating 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
5. 10:26 UTC GitHub status page · Investigating We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor
6. 10:28 UTC GitHub status page · Investigating Pull Requests is experiencing degraded performance. We are continuing to investigate.
7. 10:44 UTC GitHub status page · Resolved 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%. The cause was an internal…