GitHub favicon

GitHub outage on 2026-11-05

github.com
November 2026 5 Minor incident

GitHub had two separate incidents on 5 November, hitting Actions, Issues and Pages. The longer of the two ran 56 minutes, and both were GitHub's own infrastructure, not anything in your repository or workflow configuration.

Started

16:50 UTC

Duration

Lasted 56m

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: Issues, Actions, GitHub Pages

What happened?

The first incident started at 16:50 UTC, when GitHub reported degraded performance for Actions. By 16:52 GitHub said workflow runs might see delays or errors starting, and that a mitigation was being prepared. A mitigation landed by 17:04, and the incident was marked resolved at 17:42, giving a duration of 56 minutes. The second incident began at 23:36 UTC, this time described as degraded performance across several services including Git operations, Issues, Actions and API access, with GitHub warning that some users might see failed requests or slow responses. At 23:58 GitHub singled out Issues as still degraded. A mitigation was applied by 00:06, with GitHub reporting recovery across Git operations, Issues, Actions and API access, and the incident was resolved at 00:20, a 46 minute run. Across the day GitHub posted ten updates between the two incidents and listed three components as affected: Actions, Issues and GitHub Pages. No user reports were filed during either window. GitHub has not published a root cause for either incident beyond saying a detailed analysis will follow, and as of the resolved update, none has appeared on the record. Over the past 90 days GitHub has logged 66 incidents with a median duration of 1 hour 17 minutes, so both of these resolved faster than GitHub's typical recent incident.

Learning

UptimeRobot's own probes against GitHub's api-auth and raw-cdn components, run from both the EU and North America every 60 seconds, stayed at 100% uptime through the day, and that is not a contradiction. Those probes check whether GitHub's authentication and content delivery endpoints respond, while the incidents GitHub reported sat inside Actions workflow scheduling, Issues rendering and parts of the Git and API stack that general endpoint checks don't exercise directly. This is the shape of a lot of GitHub disruptions: the core API answers fine, but a specific feature pipeline, like Actions runners starting jobs, backs up or errors out for a defined stretch. If your own monitoring only pings GitHub's general availability, it will look green through exactly this kind of incident, because it is checking a different layer than the one that broke. 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.