Sentry logo and current status indicator

Sentry Status

Sentry is currently operational with all systems functioning normally.

Last checked Jun 13, 2026 7:34 AM UTC from Sentry's official status page

Incident History

Showing incidents from the last 15 days

Report: "Missing SDK Client Reports and Rate Limiting Outcomes"

Last update
resolved

From approximately 10:55 UTC to 11:10 UTC we experienced a loss of outcomes which power the "Stats" in the organization settings. The data loss is purely informational without impact on billing or ingested data.

Report: "Notification delivery"

Last update
resolved

This issue has been resolved.

monitoring

The issue involving some alerts not firing has been mitigated. We will continue to monitor the situation to ensure it does not reoccur.

monitoring

We have identified an issue with one of our cloud providers that might have caused some alert notifications to not fire starting at around 4:00 AM GMT+2. Since around 1:30 PM GMT+2, alert notifications are now fully operational in the US region, while delivery is still partially degraded in the EU region.

monitoring

Notifications delivery is now close to fully functional in US and DE. We have identified the root cause as caused by one of our cloud providers, and are closely monitoring the situation.

investigating

We are continuing to investigate the degraded notifications.

investigating

We are continuing to investigate the degraded notifications.

investigating

We're currently investigating degraded notification delivery.

Report: "Users unable to login to sentry.io"

Last update
resolved

Our auth systems are back operational

monitoring

We rolled back a configuration change we identified as the root cause of the issue. We'll keep monitoring our systems

monitoring

We deployed a fix and are monitoring the situation.

investigating

We are currently investigating the issue.

Report: "Elevated errors (EU)"

Last update
resolved

Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.