postmortem.io
Menu

743 entries newest

Browse

Incident

Copilot Code Review is unable to complete reviews

Read the original on the status page (external)

Copilot Code Review is unable to complete reviews

Resolved

On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot Code Review needs to complete a review. Review completion is an inherently delayed signal, because each review job takes time to start and finish, so it took longer to detect the impact.

We mitigated the incident by reverting the change.

We are working to add a faster signal for reviews that fail to complete, add deployment validation that confirms a Copilot Code Review completes end to end, improve how we track internal dependencies between services, and make our deployment pipeline more reliable to reduce our time to detection and mitigation of issues like this one in the future.

Posted Sep 28, 2026 - 22:08 UTC

Update

Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.

Posted Sep 28, 2026 - 22:08 UTC

Update

Revert of the impacted change is in flight, expect full recovery once the deployment is done.

Posted Sep 28, 2026 - 21:23 UTC

Investigating

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

Posted Sep 28, 2026 - 21:16 UTC

Original source · status page

Copilot Code Review is unable to complete reviews

https://www.githubstatus.com/incidents/169pg72gg9jr

This page is an extract. Cite the original; link here for the indexed copy.

GitHub. "Copilot Code Review is unable to complete reviews." GitHub status page, 28 Sep 2026. https://www.githubstatus.com/incidents/169pg72gg9jr (retrieved 2026-10-08 via postmortem.io)