GitHub Copilot incident
Incident with Actions and Checks API
Started
November 9, 2026 at 06:12 PM UTC
Duration
46 min
Resolved
November 9, 2026 at 06:59 PM UTC
Updates timeline
- Investigating
We are investigating reports of degraded availability for Actions
- Investigating
Actions is experiencing degraded availability. We are continuing to investigate.
- Investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
- Investigating
We're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more.
- Investigating
Pages is experiencing degraded performance. We are continuing to investigate.
- Monitoring
The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
- Resolved
On November 9, 2026, between 18:07 and 18:59 UTC, GitHub Actions experienced degraded performance. During this time, some customers saw workflow runs fail to start, update or report status correctly. An average of 28% of workflow runs were affected, peaking at 65% during the worst period of the incident. Once Actions services recovered, some jobs were left in a state that limited available concurrency until the runs were released. <br /><br />The incident occurred during a planned migration of a core Actions database from GitHub’s datacenter to a new cloud region. After the migration completed, we shifted Actions service traffic to the new region. The volume of requests exceeded the capacity and rate limits configured there, so a portion of requests were rejected and workflow updates failed. Dependent services, including Webhooks, Pages and Copilot code review, saw secondary impact. <br /><br />We mitigated impact by shifting some of the traffic back to the original region, allowing service traffic to remain within the configured limits. We then increased capacity and rate limits in the new region before gradually shifting traffic back. While this was a one-time migration event for this cluster that is now complete, we are improving how we validate capacity and limits before shifting traffic during remaining migrations, including shifting traffic in smaller steps. To address the stuck runs left after the incident, we are improving our ability to detect and mitigate these runs for future cases as well as readying an API to enable customers to address this themselves.
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