Major incident

GitHub: Incident with Actions, Pages, and Webhooks

Affected: Webhooks, Actions, Pages

Current status of GitHub: Operational — live GitHub status

Timeline

1. Oct 30, 2026, 17:50 UTC
   investigating
   We are investigating reports of degraded performance for Actions and Webhooks
2. Oct 30, 2026, 18:00 UTC
   investigating
   Pages is experiencing degraded performance. We are continuing to investigate.
3. Oct 30, 2026, 18:06 UTC
   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.
4. Oct 30, 2026, 18:32 UTC
   investigating
   All affected services have recovered following mitigation. We continue to investigate root cause.
5. Oct 30, 2026, 18:32 UTC
   monitoring
   The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
6. Oct 30, 2026, 19:23 UTC
   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.

Updates as published by GitHub (original).