Copilot Coding Agent failing to start some jobs

What to do

• Check whether you use GitHub Copilot in us. Check your stack

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

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

  Anything that failed between 2026-04-02 16:18 UTC and 2026-04-02 16:30 UTC may need a replay.

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

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

Updates from GitHub Copilot 3

1. investigatingApr 2, 2026, 4:18 PM UTC

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

   provider

2. investigatingApr 2, 2026, 4:28 PM UTC

   When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running. We are investigating.

   provider

3. resolvedApr 2, 2026, 4:30 PM UTC

   Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour. During this hour, some new jobs would time out, while others would resume once rate limiting ended. Roughly 40% of jobs in this period were affected. Once the cause of this rate limiting was identified, we were able to disable the new CCR feature via a feature flag. Once the jobs that were already in the queue were able to clear, we didn't see additional instances of rate limiting afterwards. This was the same incident declared in https://www.githubstatus.com/incidents/d96l71t3h63k

   provider

Corrections

None so far.

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