Degraded availability for GitHub Actions, GitHub Pages and Webhooks
A record of the GitHub incident on October 19, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
1 other incident(s) at different providers overlapped with this one. It may not have been limited to a single service — several providers were degraded at once.
- CursorInvestigating service degradation — Grok Bot
Derived from our own archive of official status pages across 13 providers. Items lasting more than 24 hours and unresolved items are excluded, as they would misrepresent the moment.
How big was this outage?
This outage lasted 68 minutes. Across 57 major incidents recorded for GitHub, the median duration is 89 minutes, making this the 38th longest.
Shorter than a typical outage.
Only incidents recorded as major-or-worse and already resolved are counted.
Current status
GitHub is operating normally now. This incident has been resolved.
See current GitHub status →What you can do during an outage
Source: GitHub's official status page.
Other GitHub incidents
- CCA Automations are delayed when starting an AutomationOctober 15, 2026
- [Retroactive] Actions workflow run logs delayedOctober 13, 2026
- Incident with Actions, Pull Requests and IssuesOctober 12, 2026
- Incident with Git Operations, Issues, Actions and Pull RequestsOctober 7, 2026
- Incident with Git Operations, Pull Requests and ActionsOctober 7, 2026