GitHub outage of 4 Nov 2026: what happened and how long it lasted
GitHub’s outage of 4 Nov 2026 was open on GitHub’s status page for 56 min, from 16:05 to 17:01 UTC, and affected Webhooks, Actions and Pages.
Last changed . Last checked . Source: stspg.io/pjgptg3cfc6n.
GitHub's updatesOldest first, in the vendor's own words. Times are UTC.
We are investigating reports of degraded performance for Actions and Pages
We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.
Webhooks is experiencing degraded performance. We are continuing to investigate.
Actions is experiencing degraded availability. We are continuing to investigate.
We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
The degradation has been mitigated. We are monitoring to ensure stability.
On November 4, 2026, between 15:49 UTC and 16:48 UTC, and again between 17:20 UTC and 17:55 UTC, GitHub Actions, Pages, Webhooks, Code Scanning, and Copilot coding agent experienced delays. During this time, Actions workflow runs and job status updates were delayed by up to 25 minutes. Pages deployments dropped to about 4% of normal volume, webhook deliveries dropped to about 58% of normal volume, and Code Scanning analyses and Copilot coding agent sessions were delayed. Delayed events were processed after mitigation. This incident was caused by a configuration change to an internal event-routing service that unexpectedly paused delivery of several event streams. The change depended on feature flags that were not set up as intended, which the service did not handle gracefully. We mitigated the first period by rolling back the configuration change at 16:14 UTC. The code change itself…
CauseIn GitHub's words only
This incident was caused by a configuration change to an internal event-routing service that unexpectedly paused delivery of several event streams.
GitHub has not published a post-mortem on its incident page.
Earlier at GitHub
Incident with Pull Requests, Git Operations and Issues
4 Nov 2026, major, open on the status page for 2 hIncident with Actions, Pages, and Webhooks
30 Oct 2026, major, open on the status page for 1 h 33 minDisruption with GitHub services
30 Oct 2026, critical, open on the status page for 32 minDisruption with some Copilot services
28 Oct 2026, critical, open on the status page for 1 h 15 min