- Level
- confirmed
- Worst impact
- Degraded
- Components
- Actions
- Down Index
- 40of 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 3h 10m it lasted.
Anything that failed between 2026-04-28 13:59 UTC and 2026-04-28 17:09 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 impacted performance for some GitHub services.
provider
- monitoring
Actions is experiencing capacity constraints with hosted ubuntu-latest and ubuntu-24.02, leading to high wait times. Other hosted labels and self-hosted runners are not impacted.
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We're still investigating the root cause for run start delays and failures for Actions hosted Ubuntu jobs, around 5% of jobs are impacted as of now.
provider
- investigating
We've applied a mitigation to unblock running Actions. We're continuing to monitor.
provider
- investigating
Currently less than 2% of hosted ubuntu-latest and ubuntu-24.04 runs are delayed or failing. We are continuing to monitor for full recovery.
provider
- investigating
Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.
provider
- monitoring
Actions is operating normally.
provider
- resolved
On April 28, 2026, from approximately 12:41 UTC to 17:09 UTC, GitHub Actions jobs using Standard Ubuntu 22 and Ubuntu 24 hosted runners experienced run start delays. Approximately 8% of hosted runner jobs using Ubuntu 22 and Ubuntu 24 experienced delays greater than 5 minutes or failures. Larger and self-hosted runners were not impacted. This was caused by a performance regression introduced in the VM reimage process. That reimage delay lowered the overall capacity of runners available to pick up new jobs. This was mitigated with a rollback to a known good image version. We are addressing the core issue with reimage performance and improving the granularity of reimage telemetry across our services and our compute provider to more quickly diagnose similar issues in the future. Finally, we are evaluating other rollout changes to automatically detect similar regressions.
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-1e3cd57c31
Is GitHub Actions still down?
No, this incident was resolved 2026-04-28 17:09 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
3h 10m, from 2026-04-28 13:59 UTC to 2026-04-28 17:09 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.