- Level
- confirmed
- Worst impact
- Major outage
- Components
- API Requests, Issues, Actions, Pages
- Down Index
- 63of 100
What to do
Check whether you use GitHub Actions API Requests, Issues, 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 5h 10m it lasted.
Anything that failed between 2026-07-19 23:34 UTC and 2026-07-20 04:44 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 18
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.
provider
- investigating
We have identified the cause of failures in GitHub Actions and are working to restore service.
provider
- investigating
API Requests is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Actions and Pages are experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Issues is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services. A separate incident was opened before we understood they were related. We will continue to post updates on this incident.
provider
- investigating
Pages is operating normally.
provider
- investigating
Issues is operating normally.
provider
- investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.
provider
- investigating
API Requests is operating normally.
provider
- investigating
We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.
provider
- monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
Actions has fully recovered, and we will continue to monitor the platform to ensure stability.
provider
- resolved
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates. The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal. To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.
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-0896d183a0
Is GitHub Actions still down?
No, this incident was resolved 2026-07-20 04:44 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
5h 10m, from 2026-07-19 23:34 UTC to 2026-07-20 04:44 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named API Requests, Issues, 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.