Live / GitHub / Incident
GitHub: Incident with Actions and Pages
GitHub · github.comMajor incidentResolved2026-11-04 17:01 UTC
Public — what happened
Summary
GitHub reported a major incident that began at 16:05 UTC on 2026-11-04, affecting Actions and Pages, with Webhooks also showing degraded performance shortly afterward. Around 16:34 UTC the company said it had found a problem with events that can start Actions, applied mitigations, and warned that customers might see delayed status updates for their jobs. By 16:45 to 16:49 UTC GitHub said the degradation had been mitigated across the affected services and it was monitoring stability, and the incident was marked resolved at 17:01 UTC.
Affected
Webhooks, Actions, Pages
Timeline
- Started — 2026-11-04 16:05 UTC
- Investigating — 2026-11-04 16:05 UTC (6 updates)
- Monitoring — 2026-11-04 16:48 UTC (2 updates)
- Resolved — 2026-11-04 17:01 UTC · 56 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GitHub against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GitHub: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GitHub report →
More from GitHub
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.