Minor incident

GitHub: Disruption with Copilot Cloud services

Current status of GitHub: Operational — live GitHub status

Timeline

1. Oct 29, 2026, 10:19 UTC
   investigating
   We are investigating reports of impacted performance for some GitHub services.
2. Oct 29, 2026, 10:22 UTC
   investigating
   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.
3. Oct 29, 2026, 11:01 UTC
   investigating
   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.
4. Oct 29, 2026, 11:37 UTC
   investigating
   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.
5. Oct 29, 2026, 12:33 UTC
   monitoring
   The degradation has been mitigated. We are monitoring to ensure stability.
6. Oct 29, 2026, 12:49 UTC
   resolved
   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.

Updates as published by GitHub (original).