Sentry favicon

Sentry outage on 2026-11-03

sentry.io
November 2026 3 Major incident

Sentry had two separate incidents on 3 November, one taking down the dashboard and API for 1h 42m, the other delaying span and transaction ingestion for 1h 47m. Both were on Sentry's side of the line, and both are now resolved.

Started

14:57 UTC

Duration

Lasted 1h 42m

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: Transaction Ingestion, Dashboard, API

What happened?

The first incident started at 14:57 UTC, with Sentry reporting the dashboard and API down for both US and EU customers. By 15:25 UTC Sentry said the issue was mitigated and both were operational again, and it marked the incident resolved at 16:30 UTC, a total of 1h 42m. A second, separate incident began at 15:40 UTC, this time affecting ingestion of spans and transactions. Sentry's updates narrowed this one down quickly: at 15:52 UTC it said EU was not affected and the problem was limited to US span and transaction ingestion. It identified the cause internally by 15:53 UTC and said it was working on a fix, then resolved the incident at 17:25 UTC, 1h 47m after it started, confirming that delayed data had all been processed and none had been lost. Three components were touched across the day: Dashboard, API, and Transaction Ingestion. No user reports were filed during either window, so the only account of impact is Sentry's own status page. Sentry did not publish a cause for the first incident beyond noting it affected both regions, and for the second it said only that it identified the issue, not what it was. Over the past 90 days Sentry has logged 27 incidents with a median duration of 1 hour 48 minutes, which puts both of today's incidents right in line with its usual pattern rather than standing out as unusual.

Learning

Sentry runs 436 incidents over its lifetime at a rate of 5.6 a month, so outages on its dashboard, API, or ingestion pipeline are a known and recurring feature of running on this provider, not a one-off. What today shows is a split failure: the dashboard and API problem was visible to anyone trying to load Sentry.io, while the ingestion delay was happening behind the scenes in a pipeline you don't query directly, which is why it can run for nearly two hours without you noticing anything except that your error data seems to lag. Neither of these is something an uptime check on your own endpoints would catch, because your service was fine, Sentry's intake and dashboard were not. UptimeRobot's own 30-day figures show 9 incidents against Sentry, all resolved, with a median duration of 1h 42m, which matches what Sentry itself reports and confirms this is a pattern worth watching rather than a fluke. 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.