Copilot Code Review Failing

What to do

• Check whether your product depends on GitHub. 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 1h 57m it lasted.

  Anything that failed between 2026-06-04 18:02 UTC and 2026-06-04 19:59 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 9

1. investigatingJun 4, 2026, 6:02 PM UTC

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

   provider

2. investigatingJun 4, 2026, 6:03 PM UTC

   We have identified that Copilot Code Review.  Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress.

   provider

3. investigatingJun 4, 2026, 6:22 PM UTC

   We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress, we expect mitigation in approximately 30m. GitHub Enterprise Cloud with Data Residency is not impacted.

   provider

4. investigatingJun 4, 2026, 6:52 PM UTC

   The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.

   provider

5. investigatingJun 4, 2026, 7:07 PM UTC

   The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. Customers may need to re-request Copilot Code Review.  Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.

   provider

6. monitoringJun 4, 2026, 7:07 PM UTC

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

   provider

7. monitoringJun 4, 2026, 7:41 PM UTC

   The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected.  We are continuing to monitor for full resolution.  Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.

   provider

8. monitoringJun 4, 2026, 7:59 PM UTC

   This issue is now fully resolved and Copilot Code Review is working as expected.

   provider

9. resolvedJun 4, 2026, 7:59 PM UTC

   On June 4, 2026, from 17:30 UTC to 18:55 UTC, Copilot Code Review experienced elevated failures for review requests on GitHub.com. Affected users saw “Copilot ran into an error” on pull requests when requesting a code review. During the incident window, an average of 81.6% of Copilot Code Review requests failed, with a peak failure rate of 93.9%. Approximately 36,800 code review requests failed. GitHub Enterprise Cloud with data residency was not impacted. The issue was caused by a newly released dependency used by the Copilot Code Review processing workflow. The release introduced an incompatibility with the runtime environment. Because the workflow automatically consumed the latest release, the incompatible version was picked up without sufficient compatibility validation and caused review processing to fail. We mitigated the incident by removing the problematic dependency version and redeploying the affected processing service. New code reviews began recovering at 18:44 UTC, and the failure rate returned to baseline by 18:55 UTC. Remaining timed-out work drained by 19:59 UTC. To reduce the risk of recurrence, we are pinning the dependency version instead of automatically consuming the latest release, adding compatibility checks for future releases, improving fast-failure behavior when the review processor cannot start, adding shorter timeout controls for review workflows, and improving monitoring for review completion failures.

   provider

Corrections

None so far.

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