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

As listed on GitHub’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the GitHub status & history page.

Related: GitHub status & history. SquidGrid is not affiliated with GitHub.