GitHub Copilot
No data
Last success —
No component payload
No data
Last success —
No component payload
Official incident · GitHub Copilot
resolved · 2026-09-28 21:16:39 UTC · Resolved 2026-09-28 22:08:20 UTC
Official updates
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.
Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.
Revert of the impacted change is in flight, expect full recovery once the deployment is done.
We are investigating reports of impacted performance for some GitHub services.
Could not read official status. Unknown is not operational.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
Snapshots and status changes are retained for up to 7 days; official incidents remain in the site index. Everything is generated only from official data captured by this site.