GitHub outage on October 1, 2026: Elevated request latency
GitHub reported an incident affecting GitHub for 20 minutes on 1 October 2026, from 13:37 to 13:57 UTC.
Resolved
Official incident reported by GitHub
- Started
- 13:37
- 1 Oct 2026 UTC
- Resolved
- 13:57
- 1 Oct 2026 UTC
- Duration
- 20m
- 20 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 4
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Elevated request latency
-
Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
-
Official
Investigating
We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available.
-
Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
Official
Resolved
On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returned to normal as the traffic subsided, and we have since applied additional traffic filtering to protect against similar traffic. We are improving alerting for delays in our traffic-handling infrastructure and strengthening our automated traffic protections to reduce our time to detection and mitigation.
"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.