GitHub Copilot
No data
Last success —
No component payload
No data
Last success —
No component payload
Official incident · GitHub Copilot
resolved · 2026-10-29 10:19:55 UTC · Resolved 2026-10-29 12:49:52 UTC
Official updates
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.
The degradation has been mitigated. We are monitoring to ensure stability.
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.
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 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.
We are investigating reports of impacted performance for some GitHub services.
Could not read official status. Unknown is not operational.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
Snapshots and status changes are retained for up to 7 days; official incidents remain in the site index. Everything is generated only from official data captured by this site.