Sentry favicon

Sentry outage on 2026-11-02

sentry.io
November 2026 2 Major incident

Sentry's dashboard and API went down for 4 hours and 24 minutes on 2 November 2026, affecting both US and EU customers. The fault sat on Sentry's side, confirmed by their own status page updates.

Started

15:20 UTC

Duration

Lasted 4h 24m

Source

IsDown

Next time

Sentry 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, Dashboard

What happened?

The incident started at 15:20 UTC when Sentry opened an investigation into the dashboard being down. Eight minutes later, at 15:28, Sentry widened the scope, saying the API was also affected and that both US and EU customers were hit. For nearly an hour, from 16:19 onward, Sentry's update simply confirmed they were still investigating availability issues with the UI and API, with no further detail on cause. At 17:13 Sentry reported the issue was mitigated, though they kept monitoring rather than declaring it over. The incident was finally marked resolved at 19:41, when Sentry said a fix had been deployed. That is a single filing thread with five updates across 4 hours and 24 minutes, and it is the only account on record for this incident. No user reports were filed during the window, so the only evidence here is Sentry's own narration of its outage. Two components are listed as affected: Dashboard and API. Sentry's status page never explains what caused the fault, only that it was "mitigated" and later "fixed". Over the past 90 days, Sentry has logged 25 incidents with a median duration of 2 hours and 13 minutes, so this outage ran well past that typical length. Across all time, Sentry averages 5.6 incidents a month.

Learning

UptimeRobot's own 30 day statistics show 7 incidents for Sentry, all resolved, with a median duration of 1 hour and 0 minutes, considerably shorter than this particular outage's 4 hours and 24 minutes. That gap is expected rather than a discrepancy. Your monitoring checks whether your own integration with Sentry responds, while UptimeRobot's probes check whether Sentry's dashboard and API themselves are reachable from outside. During this outage both things were true at once: your product calling Sentry's API could be failing, while anything you have pointed at Sentry directly would show the same failure Sentry itself reported. The shape of this kind of fault is that it sits entirely on the provider's side of the connection, in their UI and API layer, not in anything you configured or deployed. Watching only your own endpoints would not have told you whether the problem was yours or Sentry's, since your endpoints depend on Sentry's being up. 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.