GitHub: Increased timeouts due to surge in anonymous users
Is it fixed? Yes.
Resolved after <1 min. First reported Nov 9, 09:09 UTC, resolved Nov 9, 09:09 UTC. The vendor posted it on its status page first.
What happened
GitHub experienced performance degradation and 504 Gateway Timeout errors affecting unauthenticated users, CI jobs, and release downloads due to a surge in anonymous traffic. The issue has been successfully mitigated and services are operating normally.
What caused it?
A sudden spike in anonymous traffic overwhelmed systems, causing performance degradation and 504 gateway timeouts for unauthenticated requests.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on status page
Increased timeouts due to surge in anonymous users
Source - Official statement
Investigating: We are investigating reports of impacted performance for some GitHub services.
Source - Status changed
Status changed: new → resolved (official status page reports resolution).
- Confirmed on Bluesky post
✅ Resolved: GitHub - Increased timeouts due to surge in anonymous users
Source - Official statement
✅ Resolved: GitHub - Increased timeouts due to surge in anonymous users
Source
Evidence
2 reports · 1 Status, 1 BlueskyShow
- [1]Status First reportIncreased timeouts due to surge in anonymous users(opens official status page in a new tab)
Investigating: We are investigating reports of impacted performance for some GitHub services. Update: 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. Monitoring: The degradation has been mitigated. We are monitoring to ensure stability. Update: The problem with anonymous traffic receiving 504 status codes has been mitigated. We are…
by github status
- [2]Bluesky✅ Resolved: GitHub - Increased timeouts due to surge in anonymous users(opens the official status page in a new tab)
✅ Resolved: GitHub - Increased timeouts due to surge in anonymous users
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments92% match
FAQ
What happened in the GitHub outage?
GitHub experienced performance degradation and 504 Gateway Timeout errors affecting unauthenticated users, CI jobs, and release downloads due to a surge in anonymous traffic. The issue has been successfully mitigated and services are operating normally.
What is affected by the GitHub outage?
GitHub. Also affected at the same time: Bun.
When did the GitHub outage start and end?
It started Nov 9, 09:09 UTC and was resolved Nov 9, 09:09 UTC, after <1 min.
How do I get alerts for GitHub?
Subscribe to the GitHub RSS feed for every new GitHub incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether GitHub is down. GitHub feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 2 reports from 2 independent sources, including the vendor’s own status page.