# Increased timeouts due to surge in anonymous users

- Provider: [GitHub](https://down.guide/github)
- Level: confirmed
- Impact: Degraded
- lasted 3h 11m
- started 2026-11-09 05:59 UTC
- id: DWN-2ebef93089
- Official page: https://stspg.io/jztczfplj6yb

## 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._

## Updates from GitHub
### 2026-11-09 05:59 UTC: investigating
We are investigating reports of impacted performance for some GitHub services.

### 2026-11-09 06:30 UTC: 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.

### 2026-11-09 06:51 UTC: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.

### 2026-11-09 07:03 UTC: monitoring
The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.

### 2026-11-09 07:43 UTC: 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.

### 2026-11-09 08:16 UTC: 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.

### 2026-11-09 08:47 UTC: 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.

### 2026-11-09 09:05 UTC: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.

### 2026-11-09 09:09 UTC: monitoring
We are resolving this incident as error rates have remained low and we have prepared additional protections.

### 2026-11-09 09:09 UTC: 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.

From the builder: does your app depend on GitHub? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=github) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention GitHub.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-2ebef93089), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.