GitHub reported this minor-impact incident on its official status page on Nov 9, 2026, 05:59 UTC. It was resolved after 3h 11m.
Right now GitHub is operational. Live GitHub status →
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.
We are resolving this incident as error rates have remained low and we have prepared additional protections.
The degradation has been mitigated. We are monitoring to ensure stability.
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.
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.
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.
The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.
The degradation has been mitigated. We are monitoring to ensure stability.
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.
We are investigating reports of impacted performance for some GitHub services.
Overlapping incidents aren't necessarily related.
GitHub reported 67 incidents in the last 90 days, 28 of them major or critical. A typical incident lasted 1h 15m. See GitHub's uptime and incident history