Disruption with some GitHub services

What to do

• Check whether you use GitHub 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 3h 59m it lasted.

  Anything that failed between 2026-04-02 17:49 UTC and 2026-04-02 21:48 UTC may need a replay.

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

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

Updates from GitHub 7

1. investigatingApr 2, 2026, 5:49 PM UTC

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

   provider

2. investigatingApr 2, 2026, 5:59 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. investigatingApr 2, 2026, 6:25 PM UTC

   We are once again seeing recovery with Copilot Cloud Agent job starts. We are keeping this open while we verify this won't recur.

   provider

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

   This issue has recurred. Customers will once again experience false job starts when assigning tasks to Copilot Cloud Agent. We are still investigating and trying to understand the pattern of degradation.

   provider

5. investigatingApr 2, 2026, 8:35 PM UTC

   Although we are observing recovery once again, we expect continued periods of degradation. Work that is queued during times of degradation does eventually get processed. We continue to investigate and find a mitigation, and will update again within 2 hours.

   provider

6. monitoringApr 2, 2026, 9:48 PM UTC

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

   provider

7. resolvedApr 2, 2026, 9:48 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.

   provider

Corrections

None so far.

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