- Level
- confirmed
- Worst impact
- Degraded
- Components
- Actions
- Down Index
- 20of 100
What to do
Check whether you use GitHub 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 1h 26m it lasted.
Anything that failed between 2026-07-22 20:43 UTC and 2026-07-22 22:09 UTC may need a replay.Subscribe to GitHub's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub 5
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.
provider
- investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On July 22, 2026, between 19:36 UTC and 22:04 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 15% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 1% failed to start. At 21:49 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.
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-838835a3cc
Is GitHub still down?
No, this incident was resolved 2026-07-22 22:09 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
1h 26m, from 2026-07-22 20:43 UTC to 2026-07-22 22:09 UTC, by the times GitHub posted.
What was affected?
GitHub named Actions.
What caused it?
GitHub hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.