Disruption with some GitHub services
- Started
- 2026-04-09 16:20 UTC
- Resolved
- 2026-04-09 20:36 UTC
- Duration
- 257 minutes
- Date
- 2026-04-09
Incident Timeline
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are investigating reports of impacted performance for some GitHub services.
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are experiencing issues where jobs are being delayed to start for copilot coding agent
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
We are investigating delays processing Copilot Cloud Agent jobs
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We are continuing to investigate Copilot Cloud Agent job delays
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
We continue to investigate periodic delays in Copilot Cloud Agent job processing
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
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.
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15โ40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg