GitHub outage on November 4, 2026: Incident with Pull Requests, Git Operations and Issues
GitHub reported an incident affecting GitHub for 2 hours on 4 November 2026, from 09:49 to 11:50 UTC.
Resolved
Official incident reported by GitHub
- Started
- 09:49
- 4 Nov 2026 UTC
- Resolved
- 11:50
- 4 Nov 2026 UTC
- Duration
- 2h
- 2 hours
- Impact
- Major
- as rated by GitHub
- Updates
- 9
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Incident with Pull Requests, Git Operations and Issues
-
Official
Investigating
We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests
-
Official
Investigating
Actions is experiencing degraded performance. We are continuing to investigate.
-
Official
Investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
-
Official
Investigating
We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation.
-
Official
Investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
-
Official
Investigating
We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available.
-
Official
Investigating
The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
-
Official
Monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
Official
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.
"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.