Incident with Git Operations, Issues, Actions and Pull Requests
A record of the GitHub incident on October 7, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
3 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
- OpenAIDot in Codex may fail to create new threads
- OpenAIDegraded performance in Codex and Work mode: Dot turn failures, delayed responses, and reduced proactivity
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 48 minutes. Across 57 major incidents recorded for GitHub, the median duration is 89 minutes, making this the 42th 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.