rewindex

CompaniesGitHubIncidents

GitHub: Increased timeouts due to surge in anonymous users

MinorStatus: resolvededitedStarted Resolved (3.2 h)10 updateswww.githubstatus.com (opens in new tab)

Discussed on Hacker News

Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.

Timeline of updates

  1. investigating

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

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

  3. monitoring

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

  4. monitoring

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

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

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

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

  8. monitoring

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

  9. monitoring

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

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

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by GitHub, started 2026-11-09 05:59 UTC, resolved after 3.2 h, 10 update(s); edited after publishing.

Title
Increased timeouts due to surge in anonymous users
Vendor
GitHub
Date
URL
https://rewindex.com/company/github/incidents/c9px7cw2ghrs

GitHub profileRecent GitHub incidentsAll outages on November 9, 2026GitHub in November 2026MarkdownJSON