Sentry had 66 outages in the last 2 years totaling 51h 11m of downtime — averaging 2.7 incidents per month.
There were 66 Sentry outages since October 11, 2025 totaling 51h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We're currently investigating degraded notification delivery.
We are continuing to investigate the degraded notifications.
We are continuing to investigate the degraded notifications.
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.
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.
The issue involving some alerts not firing has been mitigated. We will continue to monitor the situation to ensure it does not reoccur.
This issue has been resolved.
We are currently investigating the issue.
We deployed a fix and are monitoring the situation.
We rolled back a configuration change we identified as the root cause of the issue. We'll keep monitoring our systems
Our auth systems are back operational
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.
We are currently investigating the issue
We have identified the cause of the issue and are deploying a fix
The fix has been deployed and we are monitoring the situation
The issue has been resolved
We are currently investigating an issue causing 500 errors and preventing access to Sentry.io organizations in the DE region. The US region remains fully operational.
We have implemented a fix and are monitoring.
Access to sentry.io is now fully operational
We are currently investigating slow page loads on sentry.io.
We have implemented a fix and are monitoring.
Latency for sentry.io has returned to normal.
We are experiencing ingestion delays for errors in the US region.
We are implementing a fix and monitoring the situation. Non-symbolicated issues are not experiencing delays.
Ingestion for symbolicated issues is back to normal.
We've put in fixes and are monitoring the situation
Ingestion and alerting back to normal
We are experiencing ingestion and alerting delays in us for spans, trace metrics, and logs
We are still investigating the issue.
We are still investigating the issue.
We are still investigating the issue.
We are continuing to investigate the issue.
We have implemented a fix. Ingestion and alerting have returned to normal operation
We are experiencing ingestion and alerting delays in us for spans, transactions, and replays
Ingestion and alerting are back to normal. We continue to monitor the situation
Ingestion and alerting are back to steady state in the US region.
We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected.
We are continuing to investigate increased UI and API timeouts and errors
We are continuing to investigate increased UI and API timeouts and errors.
We've applied a configuration change to mitigate the API/UI errors being experienced.
This incident has been resolved.
We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected
We are continuing to investigate degraded database performance.
Ingestion for spans, replays, and crons is delayed by about 15 minutes.
Our event database continues to have issues and we are actively investigating the issue.
We are working on restoring normal service. API and application performance should be improved, ingestion still has delays.
We have implemented a fix and are monitoring the situation
Database performance has returned to normal
We are currently investigating the issue.
This incident has been resolved.
We are experiencing delays on our ingestion pipeline. Explorer views are in a degraded state
Ingestion is now back to normal, we are slowly increasing write traffic to reduce intermittent API failures
The system is operating as normal, we are still investigating the root cause
This incident has been resolved.
We are currently investigating this issue.
Ingestion for spans and replays is about 10 minutes behind and catching up. API and Dashboard performance has returned to normal.
All application features are now operating as normal.
Between 07:25 UTC and 07:28 UTC, customers sending data to the legacy ingestion endpoint in our US region experienced a brief ingestion disruption lasting approximately 3 minutes. The issue has been fully resolved and ingestion is operating normally. Customers using modern DSN endpoints (`*.ingest.us.sentry.io`) were not affected. The disruption occurred during a scheduled configuration change. We're investing in additional tooling to detect and mitigate this class of issue faster. We apologize for the inconvenience and appreciate your patience.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We have identified the issue and are working on a fix.
The delay has recovered and we are monitoring the fix.
The fix has been rolled out and ingestion is recovered.
Login with SSO in Chromium browser is broken right now. Signing in using cmd or ctrl + click on the "Login with Provider" button is a workaround you can use while our team fixes the issue.
Login with SSO in Chromium browser was broken. Users experienced form submission failures due to a bug in CSP. The problem is now fixed.
US customers may experience delay in data ingestion and alerts. The issue is resolved and we are burning the backlog.
Ingestion and alerts should be back to normal
We experienced a delay in data ingestion affecting all data types between 08:40 – 08:55 UTC.
Following the ingestion delay experienced between 08:40 – 08:55 UTC, all systems are now fully operational. Data ingestion is running normally across all data types.
We have identified an issue for customers trying to access their subscription page. we are working on a fix
We are rolling out a fix
Hot fix merged, all customers can access their subscription pages now.
We performed a manual change that caused degraded performance and delayed ingestion in spans, crons, replays, and uptime that caused issues between 13:45 and 13:52 PT. The change has been cancelled and operations have returned to normal
This incident has been resolved