Sentry favicon

Sentry outage on 2026-11-11

sentry.io
November 2026 11 Major incident

Sentry had two separate incidents on 11 November, one affecting account emails and one affecting the issues feed for US users. Both were on Sentry's side: an infrastructure configuration change broke email delivery for over ten hours before anyone fixed it, and a later fault made issue queries return errors for 53 minutes.

Started

07:52 UTC

Duration

Lasted 45m

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, Email

What happened?

The first incident started well before Sentry's own update timeline suggests. Sentry says account emails stopped being delivered from 21:37 UTC on 10 November, but the first public update only went out at 07:52 UTC on 11 November, over ten hours later. The emails affected were address verification, adding new email addresses, account or organisation creation emails, organisation invites, and password resets. Alert and notification emails kept working throughout, so this was a specific slice of Sentry's email pipeline, not the whole system. Sentry's update says the cause was an infrastructure configuration change, which they reverted at 08:15 UTC, and the incident was marked resolved at 08:34 UTC, giving a stated duration of 45 minutes measured from when the public update began, not from when the underlying fault actually started. Sentry also said plainly that emails which failed during the outage window would not be resent automatically, so anyone waiting on a verification, invite or password reset had to request a new one. The second incident, hours later, was unrelated. Starting at 19:20 UTC, Sentry's US issues feed intermittently threw errors on issue queries. Sentry identified the problem by 19:46, deployed a fix by 19:58, and resolved it at 20:12, for a total of 53 minutes. No cause was given for this second incident beyond "we have identified the issue". Two components were affected across the day, Email and Dashboard, and no user reports were logged in this window.

Learning

Neither of these incidents is the kind a standard uptime check would catch. A probe hitting Sentry's dashboard or API would likely have returned a normal response the whole time, because the dashboard itself was reachable and most core functions kept working. What failed was a specific delivery pipeline for emails, and later a specific query path for the issues feed, both of which sit behind the login page and behind authenticated requests that an external check never exercises. This is a common shape: the service is up, but one function inside it is silently broken, and the only way anyone finds out is a user trying to verify an address or reset a password and getting nothing. It also means the ten-hour gap between when the email fault actually began and when Sentry told anyone about it is the kind of delay you can't see from outside unless you're specifically watching for it. Your own monitoring tells you your product is reachable and responding, which is correct and necessary, but it says nothing about whether a dependency like Sentry's email delivery is quietly failing underneath you. 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.