Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Incident with Actions, Pages, and Webhooks

Posted 30 Oct 17:50 UTC, last seen today 13:31 UTC.

Unknown Duration: the provider stated no start
7Updates posted
5Other incidents at the same time

What it affected

As the provider names it

WebhooksActionsPages

What the provider posted

Newest first
  1. 30 Oct 19:23 UTCResolvedOn 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.
  2. 30 Oct 19:23 UTCResolvedThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
  3. 30 Oct 18:32 UTCMonitoringThe degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
  4. 30 Oct 18:32 UTCUpdateAll affected services have recovered following mitigation. We continue to investigate root cause.
  5. 30 Oct 18:06 UTCUpdateWe 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.
  6. 30 Oct 18:00 UTCUpdatePages is experiencing degraded performance. We are continuing to investigate.
  7. 30 Oct 17:50 UTCInvestigatingWe are investigating reports of degraded performance for Actions and Webhooks

Around it

From the sources ChangeIntel reads; a match in time is not a cause

Keep track

What changed

  1. Status: Monitoring → Resolved · Incident state: Ongoing → Ended
  2. Status: Investigating → Monitoring
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (8)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 3 Nov 2026 · 17:41:21 UTC SummaryThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. → 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.
  2. 30 Oct 2026 · 19:26:55 UTC StageMonitoring → Resolved
  3. 30 Oct 2026 · 19:26:55 UTC Observed stateOngoing → Ended
  4. 30 Oct 2026 · 19:26:55 UTC SummaryThe degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability. → This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
  5. 30 Oct 2026 · 18:36:15 UTC StageInvestigating → Monitoring
  6. 30 Oct 2026 · 18:36:15 UTC SummaryWe 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. → The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
  7. 30 Oct 2026 · 18:10:55 UTC SummaryPages is experiencing degraded performance. We are continuing to investigate. → 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.
  8. 30 Oct 2026 · 18:05:51 UTC SummaryWe are investigating reports of degraded performance for Actions and Webhooks → Pages is experiencing degraded performance. We are continuing to investigate.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 13:11 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current