GitHub incident degrades Actions, Pages, webhooks and code search

What happened

GitHub is working through a multi-service incident that began on October 30, 2026, degrading several of its core developer services. According to GitHub's status page, the incident affected Actions, Pages and webhooks, and also produced errors in code search and live updates within the site's interface.

In the most recent update, posted at 18:06 UTC, GitHub said it had taken mitigation steps and that Actions processing and Pages deployments were showing signs of recovery. The company cautioned that the impact had not been fully resolved, and said it was continuing to monitor recovery while investigating the underlying cause.

The incident drew wider attention after the status page link appeared on the front page of Hacker News.

How the incident unfolded

The status page records a short but expanding timeline:

• At 17:50 UTC, GitHub opened an investigation into reports of degraded performance affecting Actions and webhooks.
• Ten minutes later, at 18:00 UTC, Pages was added to the list of affected services, with GitHub reporting degraded performance there as well.
• At 18:06 UTC, GitHub described delays affecting Actions workflows, Pages deployments and webhook events, alongside errors in code search and live updates. Mitigation steps had been taken, with partial recovery visible in Actions processing and Pages deployments, but the impact was not fully resolved.

In the span of roughly sixteen minutes, the incident grew from two degraded services to five distinct symptoms.

What the affected services do

The affected components sit at the center of many development workflows:

Actions is GitHub's built-in CI/CD platform, running automated build, test and deployment workflows in response to events such as pushes and pull requests. Delayed workflows mean stalled builds and tests, which can in turn block merges and hold up releases.

Pages is GitHub's static site hosting service. Degraded performance here delays deployments, leaving updated site content unpublished until the pipeline recovers.

Webhooks are the mechanism GitHub uses to push event notifications to external services, including CI systems, chat integrations, issue trackers and other automation. When webhook events are delayed, downstream tools that depend on those events can lag behind what is actually happening in a repository.

Errors in code search and live updates primarily affect developers working directly in GitHub's interface. These are friction rather than blockers, but they compound the disruption for anyone already waiting on delayed builds.

Why it matters

The incident is a reminder of how much modern software delivery funnels through a single platform. One GitHub incident simultaneously stalled CI/CD pipelines, static site deployments and the event plumbing that third-party tools rely on, which is why the disruption reached well beyond GitHub's own interface.

It also illustrates how interdependent these services are in practice: the problem surfaced at the same time across Actions, Pages, webhooks, code search and live updates, rather than appearing as separate failures.

As of the latest status update, the situation was improving but not resolved. GitHub had not yet disclosed an underlying cause, and further updates were expected on the status page. Teams that rely on GitHub for builds and deployments may want to keep monitoring until full recovery is confirmed.