Copilot gave you a degraded experience for 1h 16m on 28 October after an upstream model provider had problems. GitHub's own status page confirms the fault sat with that upstream provider, not with your setup.
Started
14:12 UTC
Duration
Lasted 1h 16m
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.
Affected components: Copilot
What happened?
GitHub opened an incident at 14:12 UTC, titled "Disruption with some Copilot services". Three minutes later it named the cause as upstream model providers, saying this was "resulting in a degraded experience across Copilot services". By 14:33 the affected models were listed specifically: GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna and MAI Code 1.1 Flash, all degraded in Copilot products and IDE surfaces. GitHub's advice at that point was to switch to another model rather than wait. At 14:55 GitHub said it had identified the root cause and was working on a mitigation, still pointing at the upstream provider. By 15:15 that mitigation was applied and GitHub reported "signs of recovery". The last update, at 15:24, still described Copilot as experiencing degraded performance while investigation continued, and the incident closed shortly after, 1h 16m after it opened. No user reports were filed during this window on UptimeRobot's side. This incident affected one component, Copilot, and GitHub never published a root cause explanation beyond naming the upstream model provider as the source. No post-mortem has been published. Over the last 90 days GitHub has logged 59 incidents with a median duration of 1 hour 21 minutes, so this one ran close to typical.
Learning
UptimeRobot's own probes against GitHub's api-auth and raw-cdn components, run from the EU and NA, stayed at 100% uptime over 24 hours and 7 days through this window, with 30 day uptime at 99.999%. That is not a contradiction. Those probes check whether GitHub's authentication and content delivery endpoints respond, and they did, the entire time. What broke was a layer further up the stack, the connection between Copilot and its upstream model providers, which is invisible to a check that only tests whether a URL answers. This is the shape of a model-provider outage generally: the surface API is reachable, but the thing it is supposed to do, generate a usable response, fails or degrades for reasons outside the surface you're monitoring. If you run a product that leans on Copilot or any AI-assisted integration, your own uptime checks against GitHub's API will look green while your users still see failures, because you are watching the wrong half of the chain. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.