- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Webhooks, Actions
- Down Index
- 50of 100
What to do
Check whether you use GitHub Actions Webhooks, 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 2h 55m it lasted.
Anything that failed between 2026-03-05 16:35 UTC and 2026-03-05 19:30 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 11
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
We are observing delays in queuing Actions workflow runs. We’re still investigating the causes of these delays.
provider
- investigating
We have applied mitigations for connection failures across backend resources and we are observing a recovery in queueing Actions workflow runs.
provider
- investigating
We are back to queueing Actions workflow runs at nominal rates and we are monitoring the clearing of queued runs during the incident.
provider
- investigating
The queue of requested Actions jobs continues to make progress. Job delays are now approximately 6 minutes and continuing to decrease.
provider
- investigating
Actions is now fully recovered.
provider
- investigating
Actions is operating normally.
provider
- investigating
Webhooks is operating normally.
provider
- resolved
On Mar 5, 2026, between 16:24 UTC and 19:30 UTC, Actions was degraded. During this time, 95% of workflow runs failed to start within 5 minutes with an average delay of 30 minutes and 10% workflow runs failed with an infrastructure error. This was due to Redis infrastructure updates that were being rolled out to production to improve our resiliency. These changes introduced a set of incorrect configuration change into our Redis load balancer causing internal traffic to be routed to an incorrect host leading to two incidents. We mitigated this incident by correcting the misconfigured load balancer. Actions jobs were running successfully starting at 17:24 UTC. The remaining time until we closed the incident was burning through the queue of jobs. We immediately rolled back the updates that were a contributing factor and have frozen all changes in this area until we have completed follow-up work from this. We are working to improve our automation to ensure incorrect configuration changes are not able to propagate through our infrastructure. We are also working on improved alerting to catch misconfigured load balancers before it becomes an incident. Additionally, we are updating the Redis client configuration in Actions to improve resiliency to brief cache interruptions.
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-1ac0c8d671
Is GitHub Actions still down?
No, this incident was resolved 2026-03-05 19:30 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
2h 55m, from 2026-03-05 16:35 UTC to 2026-03-05 19:30 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named Webhooks, 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.