outages.live
Live
SentryIncident ·

Account emails not being delivered

ResolvedOfficial update
0

Sentry account emails did not reach users. The Email and Notification Delivery - Email components had a partial outage. Sentry says the incident is resolved. It lasted from 07:52 UTC to 08:34 UTC on November 11. Emails that failed between 21:37 UTC on November 10 and 08:15 UTC on November 11 are not re-sent. Request a new verification email, invite, or password reset if needed.

State

Resolved

Started

Lasted

43 min

Worst impact

Partial outage

Timeline

2 updates
07:5208:0208:1308:2408:34
Partial outageUpdate postedTimes in UTC

Investigating

43 min 100%

Updates

Times in UTC

As posted by Sentry

Resolved

This incident was caused by an infrastructure configuration change, which we reverted at 08:15 UTC on November 11. Account emails have been delivered normally since then. Emails that failed between 21:37 UTC on November 10 and 08:15 UTC on November 11 won't be re-sent automatically. If you were waiting for an email verification, a new email address confirmation, an organization invite or a password reset during that time, please request a new one. We're sorry for the trouble.

Investigating

Since 21:37 UTC on November 10, some account emails from Sentry have not been delivered. This includes email address verification, adding new email addresses, and emails sent when you create an account or organization. Organization invites and password reset emails may also be affected. Alert and notification emails are being delivered as normal. We're investigating and working on a fix. Emails sent during this time may not arrive, so you might need to request a new verification email, invite or password reset once this is resolved. We'll post another update within the next hour.

Affected components

2
EmailNotification Delivery - Email

Sentry in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

18

Median duration

1 h 39 min

This incident

57% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 18 min
median 1 h 39 min
90 days agoToday

Other Sentry incidents

All incidents

Sentry·EU region replay ingestion latency

Sentry reports replay event ingestion latency in the EU region. The affected components are EU Replay Ingestion and EU Ingestion - EU Replay Ingestion. Sentry resolved the issue, and the outage lasted about 48 minutes.

Resolved

Sentry·Ingestion delays across all data

Sentry reported ingestion delays for all US data. The affected components were US Error, Transaction, Attachment, Profile, Replay, Span, Cron Monitoring, and Custom Metrics ingestion. Sentry resolved the incident after 70 minutes, and latency returned to normal.

Resolved

Sentry·Delays in spans and transactions processing

Sentry span and transaction ingestion had delays in the US. The affected components were US Transaction Ingestion and US Span Ingestion. Sentry resolved the issue. The incident lasted about 105 minutes. No data was lost.

Resolved

Sentry·Sentry.io dashboard and API is down

Sentry reported that the Dashboard and API did not work for US and EU customers. Sentry later reported that the issue was mitigated and the components were operational. Sentry reported that the issue is resolved. It lasted about 93 minutes.

Resolved

Sentry·Sentry dashboard is down

Sentry dashboard and API had a major outage. The problem affected both US and EU customers. Sentry reported the incident as resolved and it lasted 4 hours and 21 minutes.

Resolved

Follow Sentry

Your coding agent knows when Sentry is down, and tells you when a failure is theirs, not yours. You can also get Sentry incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sentry" and tell me if Sentry has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=sentry
Slack
/feed subscribe https://outages.live/feed.xml?providers=sentry

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane