Sentry favicon

Sentry outage on 2026-10-19

sentry.io
October 2026 19 Major incident

Sentry.io slowed to a crawl for 54 minutes on 19 October 2026, with error ingestion and alerting both affected for US region customers. The cause and fix were Sentry's, worked through on their own status page.

Started

20:39 UTC

Duration

Lasted 54m

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.

What happened?

Sentry's status page opened the incident at 20:39 UTC, reporting that Sentry.io was taking a long time to load and that ingestion might be impacted. Four minutes later, at 20:43, Sentry narrowed the scope: impact was isolated to US region customers, and alerting was affected by the same incident. That second update matters if you run on Sentry for error visibility, because it means your alerts could have gone quiet at the exact moment you needed them. By 20:53 Sentry said it had identified and addressed the cause, and was burning through an ingestion backlog built up during the slowdown. At 21:10 they reported still working through that backlog, with an estimate of 20 more minutes. The incident closed at 21:32 UTC, with backlogs processed and service back to normal, giving a total duration of 54 minutes. No post-mortem has been published beyond these five status updates, so the underlying cause of the slowdown is not on the record beyond "identified and addressed". No user reports were filed during the window on this page. Sentry's own 90 day history shows 22 incidents with a median duration of 2 hours 10 minutes, so this one resolved faster than Sentry's typical incident. Across all time, Sentry has logged 431 incidents, averaging 5.6 per month.

Learning

UptimeRobot's own 30 day checks recorded 3 incidents against Sentry, all resolved, with a median duration of 54 minutes, closely matching this one. That overlap is the point: an external check can show Sentry's edge responding while ingestion and alerting queue up behind it, because the symptom here was backlog and delay, not a hard outage that trips a simple uptime probe. If you only watch your own application's calls to Sentry, you would see slow requests or delayed alerts and have no way to tell whether that was your code, your network, or Sentry's ingestion pipeline backing up. Sentry's own status page was the only place that distinction was visible, and it took four minutes after the first report to even confirm the scope was US region only. This is the shape to recognise in your own product: things look slow or quiet, your own health checks stay green, and the real fault sits one layer upstream, in the provider's pipeline. 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.