GitHub Copilot incident

Increased timeouts due to surge in anonymous users

Minor Resolved Upstream link ↗

Started

November 9, 2026 at 05:59 AM UTC

Duration

3h 10m

Resolved

November 9, 2026 at 09:09 AM UTC

Updates timeline

  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

    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.

Get an email the next time GitHub Copilot goes down

Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

Live GitHub Copilot status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader