- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 35of 100
Summary
GitHub says it is investigating reports of impacted performance for some of its services, with the incident titled "Increased timeouts due to surge in anonymous users." The current status is investigating.
Written by anthropic/claude-haiku-5.5 from GitHub's own updates.
What to do
Check whether your product depends on GitHub. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 11m it lasted.
Anything that failed between 2026-11-09 05:59 UTC and 2026-11-09 09:09 UTC may need a replay.Subscribe to GitHub's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub 10
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- 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.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
We are resolving this incident as error rates have remained low and we have prepared additional protections.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2ebef93089
Is GitHub still down?
No, this incident was resolved 2026-11-09 09:09 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
3h 11m, from 2026-11-09 05:59 UTC to 2026-11-09 09:09 UTC, by the times GitHub posted.
What caused it?
GitHub hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.