- Level
- confirmed
- Worst impact
- Degraded
- Components
- Actions
- Down Index
- 36of 100
What to do
Check whether you use GitHub Actions Actions. 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 36m it lasted.
Anything that failed between 2026-10-23 07:29 UTC and 2026-10-23 08:05 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 5
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
We are seeing delays in results from Actions workflows being reported within GitHub starting from 07:07 UTC. Recovery is already being seen but our team is continuing to investigate and monitor performance.
provider
- monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
As of 07:27 UTC, Actions results are delivering within normal SLOs again. Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future.
provider
- resolved
On October 23, 2026, between 07:06 UTC and 07:27 UTC, GitHub Actions workflow run results were delayed. Job status, check run updates, and logs in the GitHub UI and API updated with an average delay of about 2 minutes, and some updates were delayed by up to about 7 minutes. During this window, a storage dependency that Actions uses to process workflow logs and artifacts throttled our requests. This slowed result processing, causing updates to queue up. The queue was fully processed by 07:27 UTC, shortly after the throttling stopped. To reduce the risk of recurrence, we have added several storage accounts to increase capacity, and we are working on additional steps to continue to scale. We are also working with our storage provider to understand why the throttling occurred, and improving how result processing handles storage throttling and how quickly we detect it.
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-562d84b380
Is GitHub Actions still down?
No, this incident was resolved 2026-10-23 08:05 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
36m, from 2026-10-23 07:29 UTC to 2026-10-23 08:05 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named Actions.
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.