Live / GitHub / Incident
GitHub: Incident with Actions
GitHub · github.comMajor incidentResolved2026-11-04 18:16 UTC
Public — what happened
Summary
GitHub said it began investigating reports of degraded availability for Actions at 17:40 UTC on 2026-11-04, and it rated the incident as major. By 17:53 UTC the company said it had found a problem with events that can start Actions workflows, applied mitigations, and warned that customers might see delayed status updates on their jobs. At 18:07 UTC GitHub said the degradation was mitigated and that it was monitoring for stability, and the incident was marked resolved at 18:16 UTC.
Affected
Actions
Timeline
- Started — 2026-11-04 17:40 UTC
- Investigating — 2026-11-04 17:40 UTC (2 updates)
- Monitoring — 2026-11-04 18:07 UTC
- Resolved — 2026-11-04 18:16 UTC · 36 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.