Skip to content
AI Radar by Wagner Solution
CS
Menu
worth noting Tools and apps

Approximately 70% of reviews did not complete during the Copilot Code Review service outage

clearly official source

The Copilot Code Review service experienced an outage on 28 September from 19:23 to 22:08 UTC, during which, according to GitHub, approximately 70% of requested reviews did not complete. Failed reviews were not automatically retried; users must request them again.

GitHub announced that the Copilot Code Review service had issues completing code reviews on 28 September 2026 between 19:23 and 22:08 UTC. According to the company, on average approximately 70% of requested reviews did not complete. Requests from this period were not automatically retried, and users must re-request the review on the relevant pull request.

According to GitHub, the cause was a change in a dependent service that stopped delivering the data needed to complete the review. The company rolled back the change and announced the service's recovery at 22:08 UTC. According to the company, detecting the impact was slowed by the fact that starting and completing each review takes time.

GitHub stated that it is working on faster detection of incomplete reviews, verifying the entire review at deployment, better tracking of dependencies between services, and a more reliable deployment process.

What changed

Why it matters

The service's recovery did not by itself complete previously failed reviews. Developers must resubmit the affected requests. For teams that use the service as part of their change review process, the incident highlights the need to verify that a review has actually completed, since detection of the problem can be delayed.

Two audiences, two different impacts

What this means

01

For individuals

If you requested a code review during the stated period, it may have remained incomplete even after the service was restored.

What to do For your pull request, verify whether the review requested during the incident completed, and re-request any review that failed.
More practical updates →
02

For a business

A company's change review process may have been left without the expected automated review result; according to GitHub, a delayed completion signal also extended the time needed to detect the incident.

Development
What to decide Check whether your team's change review process would catch an incomplete Copilot Code Review check.
More business impacts →
code review Copilot Copilot Code Review GitHub incident

Check the original

Event sources

clearly official source · 1 vydavatel, 0 independent. We count feeds from the same owner only once.

1
GitHub Status — incident history official service status · first detected Copilot Code Review is unable to complete reviews