- Level
- confirmed
- Worst impact
- Major outage
- Components
- Actions, Pages
- Down Index
- 58of 100
What to do
Check whether you use GitHub Actions Actions, Pages. 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 35m it lasted.
Anything that failed between 2026-05-15 08:13 UTC and 2026-05-15 08:48 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 7
- investigating
We are investigating reports of degraded availability for Actions
provider
- investigating
Pages is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- investigating
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
provider
- investigating
We are monitoring an issue that was affecting GitHub Actions and causing downstream issues in GitHub Coding Agent and GitHub Code Review Agent. The issue has resolved now but we are closely monitoring our systems for full recovery.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On May 15, 2026, from approximately 07:43 UTC to 08:48 UTC, GitHub Actions experienced a degradation that caused workflow runs to fail or experience delayed starts for a subset of customers. The incident was triggered by a planned failover of supporting infrastructure used by GitHub Actions. During that operation, an automated service discovery update did not propagate correctly, which caused traffic to be routed incorrectly and increased request timeouts in a core dependency for workflow orchestration. At peak impact, 42% of Actions runs failed. Downstream services that depend on Actions workflow execution were also impacted, including GitHub Pages and Copilot cloud services. At 08:12 UTC, responders manually corrected the service discovery routing issue. Timeout and failure rates recovered shortly after, and we continued monitoring until full stabilization was confirmed across all affected services. The incident was marked resolved at 08:48 UTC. To prevent recurrence, we are implementing failover guardrails that validate service discovery state before completing failover operations, strengthening pre-flight and post-flight verification checks, and improving dependency resilience to reduce timeout cascades during infrastructure events.
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-6c9af5da32
Is GitHub Actions still down?
No, this incident was resolved 2026-05-15 08:48 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
35m, from 2026-05-15 08:13 UTC to 2026-05-15 08:48 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named Actions, Pages.
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.