Sentry Outage History

Between July 6th 20:25 UTC and July 7th 12:25 UTC, a wrong configuration change was deployed causing over-sampling of logs, spans and metrics. The configuration change is now reverted and the issue is fixed.

We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day

The backlgo has been consumed and ingestion and alerting has returned to normal operation

We're continuing to burn down the EU spans, logs, and metrics ingestion backlog.

We are now processing the backlog in EU. Expect delays in ingestion and alerting for spans, logs, and metrics on the order of hours. We will keep this page updated as we make progress.

API and dashboards for traces, logs, spans should be restored. Ingestion is still behind but is expected to catch up in the next few hours

US ingestion is back to normal. EU ingestion is still delayed, but we are now recovering. We have created a new Statuspage incident for tracking EU, follow that for further updates: https://status.sentry.io/incidents/7tfjf5k3m0g3

We're still burning the last of our backlog in US and expect to be back to normal the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.

We're continuing burning our backlog in US and expect to be have it fully consumed within the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.

We're continuing burning our backlog in US and expect to be have it fully consumed in about 1 hour. We're continuing to investigate the delayed ingestion in our EU region.

We've taken steps to mitigate the issue in the US and we're burning our backlog and expect to be have it fully consumed in about 4 hours. We're continuing to investigate the delayed ingestion in our EU region.

We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

We're still consuming the backlog and monitoring the situation.

Backlog is being consumed and we’re still monitoring recovery

The issue was fixed and we are now monitoring the fix

We are investigating consumers for spans, logs and metrics are not ingested

All operations are back to normal, as of ~7:30PM PT

The migration has been reversed in EU and US. Application functionality is restored but there is a 45 minute delay in ingestion in the US and no delay in EU

We have identified a migration as the cause of the issue. We have reverted the migration in EU and are working on doing so in the US

We are currently investigating the issue.

Data is now processed live and the system are fully operational.

We continue to monitor the fix. Ingestion is around 45 minutes behind and improving. APIs and dashboards are functioning normally (outside of data waiting to be ingested).

We continue to monitor the situation

We continue to monitor the situation

We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01.

We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US

Our ingestion fix was not successful. We are continuing to investigate possible solutions

Our database is stabilized. We are attempting a fix to increase the ingestion rate.

We continue to investigate the issue.

We continue to investigate the issue

We continue to investigate the issue. Ingestion delays are around 40 minutes now.

We are currently investigating the issue

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.

This issue has been resolved.

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

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.

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 are continuing to investigate the degraded notifications.

We are continuing to investigate the degraded notifications.

We're currently investigating degraded notification delivery.

Our auth systems are back operational

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

We deployed a fix and are monitoring the situation.

We are currently investigating the issue.

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.

The issue has been resolved

The fix has been deployed and we are monitoring the situation

We have identified the cause of the issue and are deploying a fix

We are currently investigating the issue

Access to sentry.io is now fully operational

We have implemented a fix and are monitoring.

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.

Latency for sentry.io has returned to normal.

We have implemented a fix and are monitoring.

We are currently investigating slow page loads on sentry.io.

Ingestion for symbolicated issues is back to normal.

We are implementing a fix and monitoring the situation. Non-symbolicated issues are not experiencing delays.

We are experiencing ingestion delays for errors in the US region.

Ingestion and alerting back to normal

We've put in fixes and are monitoring the situation

We have implemented a fix. Ingestion and alerting have returned to normal operation

We are continuing to investigate the issue.

We are still investigating the issue.

We are still investigating the issue.

We are still investigating the issue.

We are experiencing ingestion and alerting delays in us for spans, trace metrics, and logs

Ingestion and alerting are back to steady state in the US region.

Ingestion and alerting are back to normal. We continue to monitor the situation

We are experiencing ingestion and alerting delays in us for spans, transactions, and replays

This incident has been resolved.

We've applied a configuration change to mitigate the API/UI errors being experienced.

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 are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected.

Database performance has returned to normal

We have implemented a fix and are monitoring the situation

We are working on restoring normal service. API and application performance should be improved, ingestion still has delays.

Our event database continues to have issues and we are actively investigating the issue.

Ingestion for spans, replays, and crons is delayed by about 15 minutes.

We are continuing to investigate degraded database performance.

We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected

This incident has been resolved.

We are currently investigating the issue.

This incident has been resolved.

The system is operating as normal, we are monitoring the fix.

Ingestion is now back to normal, we are slowly increasing write traffic to reduce intermittent API failures

We are experiencing delays on our ingestion pipeline. Explorer views are in a degraded state

All application features are now operating as normal.

Ingestion for spans and replays is about 10 minutes behind and catching up. API and Dashboard performance has returned to normal.

We are currently investigating this issue.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The fix has been rolled out and ingestion is recovered.

The delay has recovered and we are monitoring the fix.

We have identified the issue and are working on a fix.

We are currently investigating this 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.

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.

Ingestion and alerts should be back to normal

US customers may experience delay in data ingestion and alerts. The issue is resolved and we are burning the backlog.

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 experienced a delay in data ingestion affecting all data types between 08:40 – 08:55 UTC.

Hot fix merged, all customers can access their subscription pages now.

We are rolling out a fix

We have identified an issue for customers trying to access their subscription page. we are working on a fix

This incident has been resolved

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 and backlogs have been processed.

We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process.

We are continuing to mitigate load in our postgres clusters.

We are continuing to mitigate load in our postgres clusters.

We're continuing to mitigate load in our caching and postgres infrastructure.

We have identified the problem as a load issue in our caching layer and are working to mitigate the issue.

We are investigating processing delays for errors and spans in the US region

Ingestions and alerts are caught up and the incident is resolved.

Customers may experience some delay in ingestion and alerts. We are currently burning the backlog

The incident has been resolved

Ingestion is back to normal, alerts may still be delayed

We are actively mitigating the issue

We are currently investigating the issue. Some alerts may be dropped if they are for older time windows.

Ingestion and alert latency is back to normal.

We are burning the backlog and actively monitoring the progress.

US customers may experience delay in alerts. We've identified the issue and will be putting in a fix.

This incident has been resolved.

EU ingestion has been restored and latency is back to normal levels. US continues to recover and will likely be caught up within the next hour.

We have implemented a fix and are monitoring

The issue has been identified and the fix is being implemented.

We are currently investigating this issue.

Ingestion backlog has finished processing and our system is now operating normally.

Our cloud provider has resolved an underlying problem and our dashboard availability issues have been resolved. We're continuing to process our ingestion backlog and monitor the situation.

We're investigating intermittent failures loading our dashboard (all regions) and increased latency for ingestion of all events types in US

This incident has been resolved. Ingestion in our South America point-of-presence is fully functional.

We are currently investigating the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Due to a transient error, some calls to Seer are failing in EU. We identified the issue and are in the process of deploying a fix.

We have resolved the issue, and our system is now working as expected

Ingestion is back to normal, alerts may still be delayed. We will continue to monitor the recovery.

We are still continuing to process the backlog and are still monitoring the recovery.

We are still continuing to process the backlog and are still monitoring the recovery.

We are still continuing to process the backlog and are still monitoring the recovery.

We are continuing to process the backlog and are still monitoring the recovery.

We've identified and fixed the issue. We are burning the backlog and actively monitoring the progress.

We are investigating the resurfaced Zookeeper issue

We identified a problem with our Zookeeper cluster and fixed it. We now need to ingest the backlog.

We are currently investigating the issue

The incident has been resolved

We are currently investigating