- Level
- confirmed
- Worst impact
- Major outage
- Components
- Issues, Pull Requests, Actions
- Down Index
- 60of 100
What to do
Check whether you use GitHub Actions Issues, Pull Requests, 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 25m it lasted.
Anything that failed between 2026-06-08 07:11 UTC and 2026-06-08 08:36 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 8
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
Issues is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Issues is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Following investigation, we are seeing that impact is limited to unauthenticated users when accessing Pull Requests, Issues, or Actions. Our team continues to work towards mitigation with more updates to follow as we have them.
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- monitoring
The degradation affecting Actions, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On June 8, 2026, between approximately 06:30 UTC and 08:36 UTC, signed-out users experienced sustained elevated HTTP 504 errors when accessing Pull Requests, Issues, releases, patch diffs, and other related GitHub.com pages. During the incident, approximately 17% of unauthenticated requests to the affected GitHub.com endpoints returned gateway timeout errors, peaking at roughly 34% of requests at around 06:50 UTC. Some GitHub Actions workflows were also affected when they depended on release downloads or related GitHub.com endpoints. The impact lasted approximately two hours and was isolated to unauthenticated traffic; signed-in users were not affected. The issue was caused by a significant increase in abusive traffic to specific GitHub.com endpoints. This degraded our ability to respond to unauthenticated requests, causing requests to queue beyond timeout thresholds and return gateway timeout errors. We mitigated the incident by identifying the anomalous traffic pattern and applying targeted blocks at the load balancer and application layers. Error rates returned to normal and affected services were fully restored by 08:36 UTC. To reduce the likelihood and impact of similar incidents in the future, we are improving automated detection and blocking for these traffic patterns, improving our emergency traffic-blocking deployment path, and evaluating routing changes for endpoints used by both signed-out users and automated workflows.
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-1dc7934d90
Is GitHub Actions still down?
No, this incident was resolved 2026-06-08 08:36 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
1h 25m, from 2026-06-08 07:11 UTC to 2026-06-08 08:36 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named Issues, Pull Requests, 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.