‹ Back to incident history

Increased timeouts due to surge in anonymous users

ResolvedMinor incidentGitHub
Monday, November 9, 2026 13:59 – Monday, November 9, 2026 17:09 (3 hr 10 min)
Updates
ResolvedMonday, November 9, 2026 17:09

On November 9, 2026, GitHub.com experienced intermittent timeouts between approximately 05:10 and 08:15 UTC. Across that full window, 6.5% of recorded requests to github.com timed out, with a five-minute peak of 13.9% between 07:40 and 07:45 UTC. Release downloads were more affected: 38.5% of recorded requests timed out, peaking at 76% during that same five-minute interval. The two main error waves lasted about two hours and ten minutes in total, with recovery between them. The errors affected repository browsing and disrupted some CI workflows and Copilot code review jobs. Contrary to our earlier updates, follow-up analysis confirmed at least 6,236 authenticated requests that timed out, affecting activity feeds, access to uploaded attachments and repository archive downloads. Errors occurred during elevated traffic to our web infrastructure that handles unauthenticated requests. Impact was mitigated when traffic causing pressure on this system was alleviated. Our follow-up work focuses on improving capacity monitoring, traffic prioritization improvements, and automated protection against traffic spikes.

MonitoringMonday, November 9, 2026 17:09

We are resolving this incident as error rates have remained low and we have prepared additional protections.

MonitoringMonday, November 9, 2026 17:05

The degradation has been mitigated. We are monitoring to ensure stability.

InvestigatingMonday, November 9, 2026 16:47

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.

InvestigatingMonday, November 9, 2026 16:16

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.

InvestigatingMonday, November 9, 2026 15:43

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.

MonitoringMonday, November 9, 2026 15:03

The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.

MonitoringMonday, November 9, 2026 14:51

The degradation has been mitigated. We are monitoring to ensure stability.

InvestigatingMonday, November 9, 2026 14:30

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.

InvestigatingMonday, November 9, 2026 13:59

We are investigating reports of impacted performance for some GitHub services.

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview