‹ Back to incident history

Copilot Code Review is unable to complete reviews

ResolvedCritical outageGitHub
Tuesday, September 29, 2026 05:16 – Tuesday, September 29, 2026 06:08 (51 min)
Updates
ResolvedTuesday, September 29, 2026 06:08

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.<br /><br />We mitigated the incident by reverting the change.<br /><br />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.

InvestigatingTuesday, September 29, 2026 06:08

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

InvestigatingTuesday, September 29, 2026 05:23

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

InvestigatingTuesday, September 29, 2026 05:16

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

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview