Skip to content
IsAIDownNow

← GitHub Copilot status now

GitHub Copilot problems on 9 November 2026

StatusResolved
Worst verdictSome users report problems
Started
Ended
Duration3 h 55 min
Official incidentIncreased timeouts due to surge in anonymous users

Timeline

  1. We started seeing problems. Our verdict: Some users report problems.
  2. Looking normal again. We'll keep watching for 15 minutes before closing this.
  3. Our verdict changed to: Some users report problems.
  4. Looking normal again. We'll keep watching for 15 minutes before closing this.
  5. Our verdict changed to: Some users report problems.
  6. Looking normal again. We'll keep watching for 15 minutes before closing this.
  7. Our verdict changed to: Some users report problems.
  8. Looking normal again. We'll keep watching for 15 minutes before closing this.
  9. Our verdict changed to: Some users report problems.
  10. Looking normal again. We'll keep watching for 15 minutes before closing this.
  11. Our verdict changed to: Some users report problems.
  12. · official update
    Increased timeouts due to surge in anonymous users (investigating): “We are investigating reports of impacted performance for some GitHub services.” Source
  13. · official update
    Increased timeouts due to surge in anonymous users (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.” Source
  14. · official update
    Increased timeouts due to surge in anonymous users (monitoring): “The degradation has been mitigated. We are monitoring to ensure stability.” Source
  15. · official update
    Increased timeouts due to surge in anonymous users (monitoring): “The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.” Source
  16. · official update
    Increased timeouts due to surge in anonymous users (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.” Source
  17. · official update
    Increased timeouts due to surge in anonymous users (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.” Source
  18. · official update
    Increased timeouts due to surge in anonymous users (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.” Source
  19. · official update
    Increased timeouts due to surge in anonymous users (monitoring): “The degradation has been mitigated. We are monitoring to ensure stability.” Source
  20. Looking normal again. We'll keep watching for 15 minutes before closing this.
  21. Everything has looked normal for 15 minutes, so we marked this incident as resolved.

Times are shown in your local time zone. “Official update” entries quote GitHub's status page; follow the source link for the full text.

How we track incidents

We open an incident when GitHub Copilot stops looking normal or GitHub posts an official incident, and close it after 15 minutes with everything back to normal. More about our method.