Sentry favicon

Sentry outage on 2026-10-20

sentry.io
October 2026 20 Major incident

Sentry's dashboard and API stopped loading reliably for 3 hours and 20 minutes on 20 October 2026. The fault sat on Sentry's side and was theirs to fix, not something you could have patched from your end.

Started

18:20 UTC

Duration

Lasted 3h 20m

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

What happened?

Sentry's status page opened an incident at 18:20 UTC titled "Sentry.io not loading", reporting that users were having trouble loading the dashboard. Both the Dashboard and API components were marked affected, which means this was not a cosmetic frontend glitch but something touching the service's data path as well. At 18:58 Sentry said they had "mitigated the immediate problem" but were still investigating the cause, and warned that interruptions to the UI and API could continue. By 19:51 they reported impact was mitigated and both components operational again, while work continued on what they called a more durable fix. At 20:44 they moved the incident to "monitoring" status after putting in a better mitigation. The incident was closed at 21:38, 3 hours and 20 minutes after it opened, with Sentry stating plainly that the fix in place was a short term one and that they would reopen the incident if things became unstable again. That is five updates across one incident, all from Sentry, and no post-mortem has been published beyond what is quoted above. No user reports were filed during this window on this page, so the only account of impact comes from Sentry itself. Sentry's own language, three separate mentions of "mitigated" rather than "resolved" before the final close, suggests the underlying cause was still not nailed down when they stopped updating. Over the past 90 days Sentry has logged 23 incidents with a median duration of 2 hours 13 minutes, so this one ran longer than typical for them.

Learning

Sentry's dashboard and API were affected at the same time, which tells you this was not simply a UI rendering bug but something closer to the service's core serving path, the kind of fault that an external check hitting the right endpoint would catch even though a simple ping to a healthy-looking URL might not. In UptimeRobot's own monitoring over the last 30 days, 4 incidents were logged against Sentry with a median duration of 1 hour 46 minutes, all resolved, which is a different number from what you'd see if you only watched your own app's error reporting calls succeed or fail. That gap is normal: your own monitoring tells you whether your product can reach Sentry right now, but it cannot tell you whether Sentry's dashboard is rendering correctly for the humans on your team trying to read an incident. Sentry mitigating the issue three times before calling it resolved is a sign that the first fix held only partially, something you would only see by watching Sentry's own status over time rather than a single health check. If your team relies on Sentry's dashboard during an incident of your own, a day like this means the error data might still be flowing while nobody can actually look at it. 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.