Incident with several GitHub Services
API Requests, Issues, Pull Requests, Actions, Pages
Started:
Last official update:
Resolved:
Published incident duration: 89 minutes.
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 data-cleanup job that began writing to a shared database cluster at 07:33 UTC. That cl
Read the full official incident ↗
MiniCrafts groups the provider's published notice by affected product. Unconfirmed scope stays unconfirmed. Published incident duration is not a measurement of downtime for every user.
What to do
Commit locally and push later; Actions jobs usually re-queue after recovery.
Check current product status and troubleshoot · Usage limits and reset rules
Official update timeline
- · 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 data-cleanup job that began writing to a shared database cluster at 07:33 UTC. That cl
- · investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
- · investigating
We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor
- · 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
- · investigating
Actions is experiencing degraded performance. We are continuing to investigate.
- · investigating
We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests