GitHub outage, October 2026: Incident with Dependabot
GitHub reported and resolved an incident: Incident with Dependabot. It lasted 2.5 hours.
OKResolved
From GitHub's official status page, in their words.
What happened
- Started
- Resolved
- Duration
- 2.5 hours
- Impact
- minor
Why it happened
GitHub has not given a cause in its updates. We never guess one.
Timeline
Newest first. From GitHub's official status page, in their words.
- resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- investigating
We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
- investigating
We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
- investigating
We are investigating elevated errors when viewing some Dependabot alerts.
- investigating
We are investigating reports of impacted performance for some GitHub services.
What this means for a business (and what to check now)
- Retry anything that failed during the 2.5 hours.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other GitHub incidents
- Elevated errors on GPT-5.4 Nano, resolved after 38 minutes
- Incident with Actions, Pages, and Webhooks, resolved after 1.6 hours
- Disruption with GitHub services, resolved after 32 minutes
- Disruption with Copilot Cloud services, resolved after 2.5 hours
- Disruption with some Copilot services, resolved after 1.3 hours
Hear about the next GitHub incident as it starts
Free email alerts when the official status changes, with what to do while it is down.