Live / GitHub / Incident
GitHub: Incident with Actions, Pages, and Webhooks
GitHub · github.comMajor incidentResolved2026-10-30 19:23 UTC
Public — what happened
Summary
GitHub said it was looking into degraded performance affecting Actions and Webhooks starting at 17:50 UTC on 2026-10-30, and later reported that Pages was affected too. The company described delays to Actions workflows, Pages deployments and webhook events, plus errors with code search and live updates. GitHub said it took mitigation steps, and by 18:32 UTC reported that all affected services had recovered while it kept monitoring and looked into the root cause. The incident was marked resolved at 19:23 UTC, and no cause was stated in the updates provided.
Affected
Webhooks, Actions, Pages
Timeline
- Started — 2026-10-30 17:50 UTC
- Investigating — 2026-10-30 17:50 UTC (4 updates)
- Monitoring — 2026-10-30 18:32 UTC
- Resolved — 2026-10-30 19:23 UTC · 1h 33m 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 45, 2026, our weekly internet health report.