Incident with Actions, Pages, and Webhooks
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. <br /><br />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. <br /><br />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.
The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
All affected services have recovered following mitigation. We continue to investigate root cause.
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.
Pages is experiencing degraded performance. We are continuing to investigate.
We are investigating reports of degraded performance for Actions and Webhooks
About this data
Where does the incident data for GitHub come from?
Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.
How do I read the component status bars?
Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.
Why is history missing for some services?
Only services with a public official status page are included.
How is duration calculated?
Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.
See the full service list and live status in the status overview