GitHub favicon

GitHub outage on 2026-11-11

github.com
November 2026 11 Major incident

GitHub had two separate incidents on 11 November, starting at 20:22 UTC, the longer one spreading across Actions, Pages, Copilot and Webhooks. Both were GitHub-side faults, resolved within 34 minutes at the longest.

Started

20:48 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: GitHub Pages, Actions, Webhooks, Copilot

What happened?

GitHub's status page logged two incidents within about half an hour of each other on 11 November. The first began at 20:22 UTC, described as degraded performance for Webhooks, and was resolved by 20:26, a 7 minute incident. The second started at 20:48 UTC and grew into a wider problem, with GitHub posting separate updates for Pages, Actions, Webhooks and then Copilot all showing degraded availability within the same nine minutes. By 20:56 GitHub had folded these into a single statement covering "multiple GitHub products including Actions, Pages, and Copilot products." At 21:07 GitHub reported mitigation and recovery across all services, noting a backlog of Actions jobs being processed, and resolved the incident fully at 21:21, giving it a duration of 34 minutes. In both cases GitHub's updates follow the same pattern: short investigating phase, a monitoring update, then resolution with a promise that "a detailed root cause analysis will be shared as soon as it is available." No such root cause analysis is part of either record, so the cause of either incident is not on the record beyond GitHub's own description of symptoms. No user reports were filed during this window. Four components were affected across the day: Webhooks, GitHub Pages, Actions and Copilot.

Learning

UptimeRobot's own checks against GitHub's api-auth and raw-cdn endpoints from the EU and NA regions stayed green throughout, with 100% uptime over 24 hours and this incident not registered against those probes. That is consistent with what GitHub described: a degradation in specific product services like Actions, Pages, Copilot and Webhooks, not a failure of the core API authentication or CDN delivery paths that external probes exercise. A product can have a fully reachable, authenticating API while its Actions runners stall or its Pages builds fail to publish, because those are separate internal systems sitting behind the same front door. If your own product depends on Actions completing or Webhooks firing promptly, your monitoring of your own endpoints would not have caught this, because your endpoints were never the problem. GitHub's 90 day history shows 66 incidents with a median duration of 1 hour 17 minutes, so a 34 minute incident sits on the shorter side for them. 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.