GitHub had two separate incidents on 3 November 2026, hitting API Requests, Issues, Copilot and Git Operations at different points in the day. Both were GitHub-side faults, the longer one running 1h 55m against Git Operations.
Started
13:25 UTC
Duration
Lasted 34m
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: Git Operations, Issues, API Requests, Copilot
What happened?
The first incident started at 13:25 UTC as degraded performance for Copilot, and within 20 minutes GitHub's own updates show it spreading to Issues and API Requests as well. Issues was mitigated at 13:43, Copilot at 13:51, and by 13:54 GitHub said the wider degradation was mitigated, with the incident resolved at 13:56. That one lasted 34 minutes in total. A second, unrelated incident began at 20:57 UTC, this time affecting Git Operations only. GitHub's updates describe identifying the issue at 21:37, rolling out a mitigation, then seeing "significant improvement" by 22:37 while noting some customers still saw slow Git Operations. It was marked resolved at 22:41, 1h 55m after it started, making it the longer and more disruptive of the two. Across both incidents GitHub published 13 updates in total and said in both resolution notices that a detailed root cause analysis would follow, but neither incident page carries one as it stands. No user reports were filed in this window on our side. GitHub's 90 day history shows 62 incidents with a median duration of 1 hour 24 minutes, so today's shorter incident ran well under that median and the longer one sat close to it.
Learning
Our probes, which check api-auth and raw-cdn from EU and NA regions every 60 seconds, stayed at 100% uptime across 24 hours, 7 days and 30 days, and this incident was never registered against them. That is not a contradiction. Our probes test whether GitHub's authentication and raw content delivery paths answer correctly from the outside, while the incidents described here hit specific internal services, Copilot, Issues, and Git Operations, that sit behind different code paths GitHub's own status updates named directly. A degradation in Git Operations or Copilot can be entirely real for anyone using those features while a generic endpoint check keeps passing, because the two are measuring different things. This is the general shape worth remembering: a provider incident can be narrow enough to miss your external checks but still break the one feature your product depends on. Checking your own endpoints only tells you your side is up, not whether the specific GitHub service you call is degraded. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.