GitHub incident degrades webhooks, Actions, Pages and Copilot

What happened

GitHub is dealing with a wide-ranging service incident that hit several of its core products at nearly the same moment. According to the company's status page, webhooks, Actions, Pages and Copilot were all affected, with the first alerts appearing at 20:48 UTC on November 11, 2026.

The initial report said engineers were looking into reduced availability for Pages. Two further updates posted within the same minute widened the picture: Actions was described as operating with diminished availability, while webhooks were said to be performing below normal.

Eight minutes later, at 20:56 UTC, GitHub acknowledged that the problems spanned multiple products, naming Actions, Pages and Copilot, and confirmed Pages was still in a degraded state. A minute after that, Copilot was formally added to the list of services with reduced availability.

As of the final entry in the incident timeline, posted at 20:57 UTC, GitHub offered no root cause, no estimated time to resolution and no detail on how many users or repositories were affected. Every update up to that point stated only that the investigation was continuing.

What is affected

The four services named in the incident cover a large share of the developer workflow hosted directly on GitHub.

Actions is the platform's built-in continuous integration and deployment system, responsible for running build, test and release workflows whenever code changes land. When Actions availability drops, workflows can stall or fail, leaving pull merges queued and deployments waiting.

Webhooks are how GitHub tells the outside world that something happened — a push, a pull request, a release. Chat notifications, external CI triggers and custom deploy hooks all depend on them. Degraded webhook performance typically means events arrive late or not at all, so downstream automation may simply never start.

Pages hosts static sites, including project documentation and personal sites, which can become slow or unreachable during an outage. Copilot, the AI coding assistant, rounds out the list with a direct hit on developer productivity through slowed or unavailable completions and chat.

Why developers noticed

The incident surfaced on the front page of Hacker News shortly after the status updates began, according to the aggregator. That level of attention is unsurprising: a simultaneous problem affecting both event delivery and build execution touches the two mechanisms most teams rely on to ship software.

Why it matters

GitHub functions as infrastructure for a huge portion of the software industry, and this incident degraded the layers that make repositories active rather than passive. Actions running unreliably means builds and tests cannot be trusted or completed; webhooks misfiring means external systems may never learn that code changed at all. The combination is close to a worst case for release pipelines, since both the trigger and the executor of automation are compromised at once.

The inclusion of Pages and Copilot widens the blast radius beyond CI/CD, taking documentation and project sites down while simultaneously degrading the tool many developers use to write code. It is also a reminder of concentration risk: when one vendor's webhook and CI services wobble, thousands of independent teams and their pipelines feel it together, and a single status page becomes the only source of truth about when shipping can resume.

What to watch

GitHub's status page is the authoritative channel for updates, and resolution notices should appear there first. Teams that depend on GitHub automation should treat this as a prompt to verify recent workflow runs, re-check any deployments that appeared to complete silently, and confirm that webhook-driven integrations received their events once service recovers — delayed or missed deliveries often surface only after an incident is formally closed.