Disruption with Copilot Cloud services

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 30m it lasted.

  Anything that failed between 2026-10-29 10:19 UTC and 2026-10-29 12:49 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 6

1. investigatingOct 29, 2026, 10:19 AM UTC

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

   provider

2. investigatingOct 29, 2026, 10:22 AM UTC

   We are experiencing increased failures and latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app.

   provider

3. investigatingOct 29, 2026, 11:01 AM UTC

   We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app.

   provider

4. investigatingOct 29, 2026, 11:37 AM UTC

   We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. We are actively applying mitigations and monitoring for recovery.

   provider

5. monitoringOct 29, 2026, 12:33 PM UTC

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

   provider

6. resolvedOct 29, 2026, 12:49 PM UTC

   On October 29, 2026, between 05:50 UTC and 12:40 UTC, Copilot agent sessions on GitHub.com and in VS Code were degraded. Live session updates often failed to load, and on average 2.14% of requests to the agent sessions service failed, with a peak of 8.61%. For about 10 minutes around 09:20 UTC, up to 40% of requests to list or create agent sessions failed. Copilot Chat on GitHub.com showed degraded agent session features during this time. The issue occurred when a large increase in task-list requests from a client experiment overloaded the cache that supports the agent sessions service. We mitigated the impact by increasing cache capacity, reducing nonessential load on the cache, and disabling the client experiment. We are moving rate limiting to separate infrastructure, reducing client polling, and improving our alerting so we can detect and respond to this type of overload faster.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.