GitHub outage on October 5, 2026: Disruption with some GitHub services
GitHub reported an incident affecting GitHub for 1 hour 45 minutes on 5 October 2026, from 23:47 to 01:32 UTC.
Resolved
Official incident reported by GitHub
- Started
- 23:47
- 5 Oct 2026 UTC
- Resolved
- 01:32
- 6 Oct 2026 UTC
- Duration
- 1h 45m
- 1 hour 45 minutes
- Impact
- Major
- as rated by GitHub
- Updates
- 3
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Disruption with some GitHub services
-
Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
-
Official
Investigating
Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
-
Official
Resolved
On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages. This was caused by a networking failure, which disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database services. We mitigated the incident by shifting the database traffic to a healthy region. We are working to make regional database failover faster and more complete, reduce timeouts so these pages fail fast instead of hanging, and add latency-based alerting to reduce our time to detection and mitigation of issues like this one in the future. We continue to partner with our cloud provider to understand the underlying network failure.
"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.