GitHub outage on October 7, 2026: Incident with Git Operations, Issues, Actions and Pull Requests
GitHub reported an incident affecting GitHub for 48 minutes on 7 October 2026, from 17:17 to 18:04 UTC.
Resolved
Official incident reported by GitHub
- Started
- 17:17
- 7 Oct 2026 UTC
- Resolved
- 18:04
- 7 Oct 2026 UTC
- Duration
- 48m
- 48 minutes
- Impact
- Critical
- as rated by GitHub
- Updates
- 5
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Incident with Git Operations, Issues, Actions and Pull Requests
-
Official
Investigating
We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
-
Official
Investigating
We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
-
Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
Official
Monitoring
All systems have recovered. We have applied mitigations and do not anticipate another recurrence.
-
Official
Resolved
On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7
"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.
Does your product depend on GitHub?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.