GitHub outage on November 8, 2026: Increase in timeouts for some unauthenticated users

GitHub was down for 22 minutes on 8 November 2026, from 10:50 to 11:12 UTC, as measured by HostTracker's checkpoints. GitHub posted its first update at 10:36 UTC and marked the incident resolved at 12:32 UTC.

github.com All times UTC

Resolved

Outage measured by HostTracker's checkpoints

Started: 10:50; 8 Nov 2026 UTC
Ended: 11:12; 8 Nov 2026 UTC
Duration: 22m; 22 minutes
Checkpoints: 1; reported a failure
Most common error: Timeout; as reported by our checks

Timeline

All times UTC.

Official incident from GitHub

Increase in timeouts for some unauthenticated users

Resolved Minor impact 8 Nov 2026 10:36 UTC View on GitHub's status page

10:36 Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
11:01 HostTracker checks

First failed check from New York, United States: Timeout.
11:12 HostTracker checks

Our checks pass again: GitHub is back up after 22 minutes.
11:16 Official
Investigating
We are continuing to investigate degraded performance primarily for unauthenticated users.
11:20 Official
Investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
11:50 Official
Investigating
We've identified a problematic component and are working to redeploy it.
11:56 Official
Investigating
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
12:29 Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
12:32 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."HostTracker checks" rows are our own measurements.

What our checkpoints saw

All times UTC.

The first failed check is the top row, and the recovery is the last one. A row marked "x N" stands for several consecutive checks with the same result from that checkpoint.

Individual checks recorded during the GitHub outage on 8 November 2026, all times UTC
Time (UTC)	Location	Result	Error
8 Nov 11:01	New York, United States	Failedx 2	Timeout

Response time around the outage

52ms low · 40002ms peak

8 Nov 09:29 to 8 Nov 11:01 UTC

The shaded band is the outage window. Points are averaged per bucket across the checkpoints that answered, so a gap in the line is a period where nothing answered at all.

Previous outage

14 Sep 2026 14:40 UTC

Next outage

This is the most recent outage we recorded.

All GitHub incidents Live GitHub status Every service we track

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.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.