Increased timeouts due to surge in anonymous users

Summary

Increased timeouts due to surge in anonymous users

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.

• Started

  Nov 9, 2026 · 5:59 AM

• Resolved

  Nov 9, 2026 · 9:09 AM

• Duration

  3h 10m

• Severity

  Minor

• ◐

  Investigating

  Nov 9 · 5:59 AM GitHub

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

• ◐

  Investigating

  Nov 9 · 6:30 AM GitHub

  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

  Nov 9 · 6:51 AM GitHub

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

• ◉

  Monitoring

  Nov 9 · 7:03 AM GitHub

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

• ◐

  Investigating

  Nov 9 · 7:43 AM GitHub

  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.

• ◐

  Investigating

  Nov 9 · 8:16 AM GitHub

  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.

• ◐

  Investigating

  Nov 9 · 8:47 AM GitHub

  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.

• ◉

  Monitoring

  Nov 9 · 9:05 AM GitHub

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

• ◉

  Monitoring

  Nov 9 · 9:09 AM GitHub

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

• ✓

  Resolved

  Nov 9 · 9:09 AM GitHub

  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.