GitHub outage on September 28, 2026: Copilot Code Review is unable to complete reviews
GitHub reported an incident affecting GitHub for 52 minutes on 28 September 2026, from 21:16 to 22:08 UTC.
Resolved
Official incident reported by GitHub
- Started
- 21:16
- 28 Sep 2026 UTC
- Resolved
- 22:08
- 28 Sep 2026 UTC
- Duration
- 52m
- 52 minutes
- Impact
- Critical
- as rated by GitHub
- Updates
- 4
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Copilot Code Review is unable to complete reviews
-
Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
-
Official
Investigating
Revert of the impacted change is in flight, expect full recovery once the deployment is done.
-
Official
Investigating
Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.
-
Official
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.
"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.
Does your product depend on GitHub?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.