- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Webhooks, Actions, Pages
- Regions
- us
- Down Index
- 48of 100
What to do
Check whether you use GitHub Pages Webhooks, Actions, Pages in us. 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 33m it lasted.
Anything that failed between 2026-10-30 17:50 UTC and 2026-10-30 19:23 UTC may need a replay.Subscribe to GitHub Pages's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-pages works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
We continue to investigate root cause.Read the postmortem
Updates from GitHub Pages 6
- investigating
We are investigating reports of degraded performance for Actions and Webhooks
provider
- investigating
Pages is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We continue to investigate delays affecting Actions workflows, Pages deployments, and webhook events, along with errors affecting code search and live updates. We have taken mitigation steps. Actions processing and Pages deployments are showing signs of recovery, but impact has not fully resolved. We are monitoring recovery and investigating the underlying cause.
provider
- investigating
All affected services have recovered following mitigation. We continue to investigate root cause.
provider
- monitoring
The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On October 30, 2026, from 17:50 to 18:32 UTC, Actions, Pages, and Webhooks experienced degraded performance. Actions workflow processing, Pages deployments, and webhook deliveries were delayed, and code search and live updates returned errors. Some Actions queues took additional time to drain after mitigation, and the incident was resolved at 19:23 UTC. The impact was triggered by maintenance on a cloud network gateway connecting an Actions service in the GitHub data center to Redis clusters in the Central US Azure region. The service's Redis client retried aggressively and redialed those connections. That produced a connection storm that saturated the gateway, with about 90% of connection attempts failing. Other services sharing the same network path were degraded as well. We mitigated the incident by removing the affected resources from rotation, which ended the connection storm and allowed the gateway to recover. We have already reduced the number of connection retries in the impacted service and are further improving retry behavior with jittered backoff, shorter connect timeouts, and retry budgets. We are also working with our infrastructure team to make GitHub more resilient to gateway maintenance.
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-0dd00a7ef8
Is GitHub Pages still down?
No, this incident was resolved 2026-10-30 19:23 UTC. For GitHub Pages's live state, see https://down.guide/github-pages.
How long did it last?
1h 33m, from 2026-10-30 17:50 UTC to 2026-10-30 19:23 UTC, by the times GitHub Pages posted.
What was affected?
GitHub Pages named Webhooks, Actions, Pages in us.
What caused it?
GitHub Pages wrote: "We continue to investigate root cause." The postmortem: https://stspg.io/5cd2m4n59spv
Where does this come from?
GitHub Pages's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.