GitHub outage on November 9, 2026: Increased timeouts due to surge in anonymous users

GitHub has reported an incident affecting GitHub since 05:59 UTC on 9 November 2026 (2 hours 54 minutes so far).

github.com All times UTC

Open

Official incident reported by GitHub

Started: 05:59; 9 Nov 2026 UTC
Status: Open; not resolved yet
Duration: 2h 54m; 2 hours 54 minutes so far
Impact: Minor; as rated by GitHub
Updates: 7; posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Increased timeouts due to surge in anonymous users

Investigating Minor impact 9 Nov 2026 05:59 UTC View on GitHub's status page

05:59 Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
06:30 Official
Investigating
We are debugging a spike in anonymous traffic. Some users who are not logged in may see errors on the site. CI jobs and release downloads may fail with a 504 Gateway Timeout status if they make anonymous calls.
06:51 Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
07:03 Official
Monitoring
The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.
07:43 Official
Investigating
We have observed a repeated increase in 504 errors for anonymous and unauthenticated traffic, including users who are not logged in and release downloads. We are continuing to investigate and apply mitigations.
08:16 Official
Investigating
We are continuing to observe high rates of 504 errors for anonymous requests. We are continuing to work on mitigation. Logged-in users and authenticated requests are unaffected.
08:47 Official
Investigating
Error rates have declined again, and we’re preparing targeted traffic controls while monitoring for a recurrence. Logged-in users and authenticated requests have not been affected.

"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.

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.