GitHub favicon

GitHub outage on 2026-11-12

github.com
November 2026 12 Minor incident

GitHub had two separate incidents on 12 November 2026, one affecting Webhooks and one affecting email delivery for sign-in and notifications. Both were on GitHub's side, the first lasting 53 minutes and the second running 2h 9m.

Started

18:43 UTC

Duration

Lasted 53m

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: Webhooks

What happened?

GitHub's status page logged two incidents this day, starting at 18:43 UTC. The first was described as an "Incident with Webhooks API", with GitHub saying the Webhooks API was "experiencing timeouts and errors impacting about 1% of customer traffic." That one ran 53 minutes, with GitHub reporting traffic had recovered by 19:20 UTC before marking it resolved at 19:33 UTC. The second incident started at 19:36 UTC and was labelled "Disruption with Email Delivery". GitHub said users "may be unable to sign-in, verify e-mail addresses, reset passwords, or receive e-mail notifications due to degradation with an upstream e-mail provider." That incident ran 2h 9m, the longest of the day, and GitHub later clarified that only users whose email was hosted by the affected upstream provider were impacted, while others saw normal service. It was marked resolved at 21:43 UTC. No independent user reports were filed during either window. GitHub's component list names only Webhooks as affected, though the email disruption clearly touched a separate, unlisted dependency on an upstream provider. In both cases GitHub says a root cause analysis will be shared when available, but none has been published yet.

Learning

This is a case where the fault sat in GitHub's dependencies rather than in the core service you'd normally watch. Webhooks timeouts and a third-party email provider degradation are both things that live upstream of your own endpoints, so pinging your product's health checks during this window would have told you nothing useful. Your own probes watching GitHub's api-auth and raw-cdn components stayed green at 100% uptime over 24 hours, and that's correct, because those specific components weren't where the trouble was. GitHub's own status page is the only record of what actually broke, and even that took time to narrow down, moving from "some GitHub services" to webhook timeouts to an identified upstream email provider. The general shape to watch for is partial, percentage-based degradation, GitHub itself said only about 1% of webhook traffic was affected, which is the kind of fault that slips past binary up or down checks entirely. 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.