- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Actions, Codespaces
- Down Index
- 49of 100
What to do
Check whether you use GitHub Actions Actions, Codespaces. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 3m it lasted.
Anything that failed between 2026-07-07 14:14 UTC and 2026-07-07 16:17 UTC may need a replay.Subscribe to GitHub Actions's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-actions works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub Actions 9
- investigating
We are investigating reports of degraded performance for Actions and Codespaces
provider
- investigating
Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time. Actions runs in progress are continuing successfully.
provider
- investigating
Codespaces is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time. Retries may be successful. Actions runs and codespaces in progress are continuing successfully. We are continuing to investigate the source of these errors.
provider
- investigating
Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful. We continue to investigate the source of these errors.
provider
- investigating
Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation.
provider
- investigating
We have rolled out the mitigation and are seeing recovery.
provider
- monitoring
The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests, though retries were frequently successful. In-progress Actions runs and Codespaces were not impacted and continued successfully. This was due to a recent change that did not deliver the expected performance and, under certain conditions, caused downstream errors. We mitigated the incident by rolling back the change, after which the affected services recovered. We are working to improve the resilience of our services to these conditions and to strengthen our monitoring to reduce our time to detection and mitigation of issues like this one in the future.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-966fc9eafd
Is GitHub Actions still down?
No, this incident was resolved 2026-07-07 16:17 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
2h 3m, from 2026-07-07 14:14 UTC to 2026-07-07 16:17 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named Actions, Codespaces.
What caused it?
GitHub Actions hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub Actions's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.