GitHub favicon

GitHub outage on 2026-11-10

github.com
November 2026 10 Major incident

GitHub's own status page logged an incident affecting Actions and Pull Requests starting at 16:10 UTC and lasting 1h 44m. If workflows triggered from pull requests were delayed or failing for you during that window, the fault sat on GitHub's side, not yours.

Started

16:10 UTC

Duration

Lasted 1h 44m

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: Actions, Pull Requests

What happened?

GitHub opened the incident at 16:10 UTC, reporting degraded performance for Actions and Pull Requests. By 16:31 the description had sharpened to elevated response times for Git operations and pull requests, with Actions workflows triggered from pull requests specifically called out as delayed. Over the next hour GitHub posted a string of updates tracking the two affected components separately: Actions degraded again at 16:39, then recovering by 17:28 when GitHub said it was operating normally, while Pull Requests was still listed as degraded at 17:12 and showing only partial improvement by 17:46. The 17:46 update is explicit that some users continued to experience delays and failures in pull request processing even as Actions recovered, which tells you the two components did not fail and heal in lockstep. GitHub resolved the incident at 17:55, a total of nine updates across 1h 44m. The resolution note says a detailed root cause analysis will be shared once available, but as of that update no such analysis is on record, so the cause of the slowdown is not known from GitHub's own account. No user reports were filed in this window on this page, so the only description of impact comes from GitHub itself. For context, GitHub has logged 68 incidents in the last 90 days with a median duration of 1 hour 19 minutes, and this one ran a bit longer than that median.

Learning

UptimeRobot's own checks against GitHub's api-auth and raw-cdn components, run from the EU and North America every 60 seconds, show 100% uptime over 24 hours and 99.964% over 30 days, with this incident not registered against those probes. That is not a contradiction. Actions and Pull Requests are specific application features sitting behind GitHub's edge, and a slowdown in workflow processing or pull-request response times can happen while the authentication and content-delivery endpoints those probes watch stay fully responsive. This is the shape to watch for in your own product: a feature-level degradation that never touches the basic reachability checks you or any external monitor would run against a provider's front door. If your integration depends on Actions or pull-request automation, pinging GitHub's API status alone would not have caught this one. Your own monitoring covers your half of the chain, the deploy pipeline, the webhook handler, the retry logic. UptimeRobot now watches the provider's half too, so next time something like this happens 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.