GitHub favicon

GitHub outage on 2026-11-08

github.com
November 2026 8 Minor incident

GitHub's API Requests component degraded for 1h 58m on 8 November 2026, chiefly hitting unauthenticated users with timeouts. GitHub traced it to a problematic component it had to redeploy, not anything on your side.

Started

10:36 UTC

Duration

Lasted 1h 58m

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: API Requests

What happened?

GitHub opened this incident at 10:36 UTC, investigating reports of impacted performance across its services. By 11:16 it had narrowed the problem to degraded performance primarily affecting unauthenticated users, and by 11:20 it named the affected component directly: API Requests. At 11:50 GitHub said it had identified a problematic component and was working to redeploy it, which is the closest thing to a cause on record here. By 11:56 the degradation was mitigated and GitHub was monitoring for stability, and the incident was marked resolved at 12:32, giving a total duration of 1h 58m. GitHub said a detailed root cause analysis would follow once available, but as of this resolved update none has been attached. This was a single incident affecting one component, API Requests, out of the one component tracked on this page. No user reports were filed during the window on this page's record. GitHub's own update cadence, six updates over roughly two hours, suggests this was taken seriously internally even though the public language stayed measured throughout. Over the last 90 days GitHub has logged 67 incidents with a median duration of 1 hour 17 minutes, so this one ran longer than typical.

Learning

UptimeRobot's own probes against GitHub's api-auth and raw-cdn components, run from both EU and NA regions every 60 seconds, registered this incident, with 24-hour uptime dropping to 98.918% while the 7-day and 30-day figures stayed much closer to full. That is the useful split: GitHub's status page described a timeout problem hitting mainly unauthenticated requests, which is exactly the kind of partial, user-segment-specific failure that can slip past a simple up-or-down check on your own endpoint while still showing up clearly in sustained probing against the provider's own API surface. If your product authenticates most of its calls, you may have seen little to nothing, while unauthenticated integrations or public-facing features could have timed out for nearly two hours. This is a provider-side fault, in a component GitHub itself had to redeploy, and no action on your infrastructure would have prevented or shortened it. Your own monitoring tells you whether your service is reachable, but it cannot tell you whether GitHub's API layer underneath you is degraded. That is the gap this page exists to close: your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.