rewindex

CompaniesGitHub CopilotIncidents

GitHub Copilot: Incident with Actions, Pages, and Webhooks

MajorStatus: resolvededitedStarted Resolved (1.6 h)6 updateswww.githubstatus.com (opens in new tab)
Summary

GitHub reported a minor incident involving degraded performance for Actions and Webhooks starting 2026-10-30 17:50 UTC. The incident remained under investigation and was still open when archived, with 0 min elapsed at the last update; no cause or fix was stated.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: ActionsPagesWebhooks

Discussed on Hacker News

Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.

Timeline of updates

  1. investigating

    We are investigating reports of degraded performance for Actions and Webhooks

  2. investigating

    Pages is experiencing degraded performance. We are continuing to investigate.

  3. 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. investigating

    All affected services have recovered following mitigation. We continue to investigate root cause.

  5. monitoring

    The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.

  6. resolvedEdited

    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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).

Cite this

Status incident (vendor impact label: major) posted by GitHub Copilot, started 2026-10-30 17:50 UTC, resolved after 1.6 h, 6 update(s); edited after publishing.

Title
Incident with Actions, Pages, and Webhooks
Vendor
GitHub Copilot
Date
URL
https://rewindex.com/company/github-copilot/incidents/pwxsjgnvrk6b

GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on October 30, 2026GitHub Copilot in October 2026MarkdownJSON