GitHub's Copilot Code Review feature failed to complete reviews for 53 minutes on 28 September 2026. GitHub traced it to a change that needed reverting, and the fault sat entirely on their side.
Started
21:16 UTC
Duration
Lasted 53m
Source
IsDown
Next time
GitHub is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
GitHub opened the incident at 21:16 UTC, saying it was investigating reports of impacted performance for some GitHub services. By 21:23 it had identified a specific fix: a revert of the change that caused the problem, with full recovery expected once that deployment finished. The incident closed at 22:08 UTC, 53 minutes after it began, with GitHub stating a detailed root cause analysis would follow once available. No such analysis has been published yet, so the underlying cause of the bad change is not on the record beyond "revert in flight". GitHub's own component list for this incident is empty in the record, and the only named symptom throughout is Copilot Code Review being unable to complete reviews. No user reports were filed during the window. This was a single incident, not a string of them, and it resolved quickly relative to GitHub's own history: the 90 day median incident length for GitHub is 1 hour 22 minutes, and this one ran under an hour. GitHub has logged 64 incidents in the past 90 days and roughly 13 a month going back over its full history, so a short-lived issue affecting one Copilot feature sits well within its usual pattern rather than standing out from it.
Learning
UptimeRobot's own probes against GitHub's api-auth and raw-cdn components, checked every 60 seconds from both the EU and North America, stayed at 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident was not registered against them. That is not a contradiction. Copilot Code Review is an application-layer feature built on top of GitHub's core API and CDN, so a bad deployment can break review completions while authentication and raw file delivery keep answering normally. This is the shape to watch for: a vendor-reported incident that never shows up as downtime on basic reachability checks, because the break is in logic, not in the connection. If your product depends on Copilot reviews specifically, pinging GitHub's API to confirm it is "up" would have told you nothing useful during this window. Your own monitoring covers your half of the stack, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
