GitHub Copilot incident
Incident with Actions
Started
November 5, 2026 at 04:50 PM UTC
Duration
52 min
Resolved
November 5, 2026 at 05:42 PM UTC
Updates timeline
- Investigating
We are investigating reports of degraded performance for Actions
- Investigating
Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
- Monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- Resolved
Between 16:39 and 16:57 UTC on November 5, 2026, some customers experienced failures starting workflow runs in GitHub Actions and Checks, and some in-progress runs failed. At peak, about 3% of workflow runs failed to queue, and roughly 0.21% of in-progress runs failed.<br /><br />The cause was resource exhaustion in a database service that stores Actions Checks data. Bursts of highly concurrent, large read requests put the service under memory pressure, which caused it to stall and reject requests.<br /><br />We mitigated the incident by failing over the affected database host. To prevent a recurrence, we have increased memory capacity across the affected database fleet. We will also be limiting concurrency of large queries to prevent heavy read traffic from causing a broad failure of critical workflows.
Get an email the next time GitHub Copilot goes down
Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.
Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.
Live GitHub Copilot status
Current indicator + 24h latency
All incidents
Cross-service timeline
Subscribe via RSS
Atom feed for any reader