Sentry Outage History
Past incidents and downtime events
Complete history of Sentry outages, incidents, and service disruptions. Showing 50 most recent incidents.
September 2026(4 incidents)
Ingestion is delayed in US
3 updates
Ingestion is now operating normally.
We are continuing to monitor delayed ingestion.
We are investigating degraded ingestion in US.
Sentry.io elevated number of 500 errors
3 updates
Issue fully resolved
Issue were identified and fixes were applied. We continue to monitor situation
During migration to new control silo region we started to observe increased number of 500 errors. Migration procedure was rolled back.
Span ingestion is degraded in US
7 updates
Spans ingestion is now operating normally.
Latency is almost fully recovered.
A fix has been implemented, and latency is coming down.
We are continuing to investigate an issue that affects spans ingestion latency
We are continuing to investigate an issue that affects spans ingestion latency
We are continuing to investigate an issue that affects spans ingestion latency
We are experiencing slow ingestion for spans in US
Sentry requests timing out / 504's
4 updates
This incident has been resolved.
We're monitoring the implemented fix
We identified the issue and rolled out a configuration change
We are currently investigating what's going on and why requests timing out
August 2026(11 incidents)
Ingestion backlog
7 updates
This incident has been resolved.
Our systems are recovering from an ingestion backlog, webhooks are currently delayed
Our systems are recovering from an ingestion backlog
API is experiencing issues
The fix has been deployed and our ingestion backlogs are recovering
We have identified the culprit and are rolling out a fix
we are investigating a failure in our infrastructure that is delaying ingestion
sentry.io is not available
10 updates
Our latency is now back to normal. Incident resolved
Our latency is now back to normal. We'll keep monitoring our systems a few more time before declaring the incident as resolved
We keep monitoring our systems while we recover to our usual latency
We are continuing to monitor while our systems recover after an issue that affected the availability of our product and API
We have identified and mitigated an issue that affected the availability of our product and API, and are now monitoring while our systems recover
We are continuing to investigate an issue that affects the availability of our product and API
We are continuing to investigate an issue that affects the availability of our product and API
We are continuing to investigate an issue that affects the availability of our product and API
We are continuing to investigate an issue that affects the availability of our product and API
We are currently investigating an issue that affects the availability of our product and API
Issues performance is degraded in the US
5 updates
The issue has been resolved
We have put a fix into place and are monitoring the situation
We have put a fix into place and are monitoring the situation
We have identified a potential cause of excess traffic and are working on a fix.
We are experiencing slower page loads and API responses due to a database issue in us
Errors alerting degraded in US region
4 updates
Error alerting is back to normal.
We have identified the issue and implemented a fix.
We are continuing to investigate the issue
We are investigating delays in error alerts in the US region, up to 10 minutes
Alert backlogs in US
4 updates
The problem has been resolved, all backlogs have cleared and everything is operational again.
We have implemented a fix and the systems are recovering. We are monitoring to ensure that backlogs are proessed.
We have identified the cause and are working to determine a mitigation. This is only affecting US right now.
We are currently investigating a delay in evaluating alerts in the US region.
Span & Transaction ingestion delayed in DE
10 updates
All backlogs have been processed.
We continue to make progress on the spans backlog with an estimated completion time of 15 minutes.
We're continuing to make progress on the span ingestion backlog in US.
We've recovered all ingestion latency in DE. In US, errors have processed their backlog and we continue to make progress on spans in US.
The problematic change has been reverted and we're processing backlogs.
The problematic change has been reverted and we're processing backlogs.
We've identified the source of latency and are reverting that change.
We are currently investigating ingestion delays for spans, transactions and alerts in DE and US
We are currently investigating ingestion delays for spans and transactions in DE and US
We are currently investigating ingestion delays for spans and transactions in DE
Error ingestion delays in US
3 updates
Backlogs have been processed
We've mitigated the source of ingestion latency and are processing the backlog.
We are currently investigating error ingestion latency in US.
Delayed Error ingestion in our US region
5 updates
The backlog has been processed
We're processing new events and alerts in realtime, and continue to process the tail of the backlog.
A fix has been made and the backlog is being processed.
We've identified the root cause and are actively working on mitigation.
We are actively investigating this issue.
Sentry API timeouts (US)
3 updates
API performance has returned to expected levels.
API performance has returned to expected levels. We are continuing to monitor.
We are currently investigating reports of API timeouts for the Sentry API in our US region.
Spans, crons, logs ingestion delayed in US region
4 updates
The ingestion delay is resolved
Ingestion latency for spans, crons, and logs is back to normal levels.
We've put a fix in place and are monitoring. We anticipate catching up to ingestion within 1 hour
We are currently investigating the issue
Delayed Error ingestion in our US region
5 updates
We've processed all backlogged events and have fully recovered.
We're processing new events in real time, and are working through a backlog of events now.
We've identified the issue causing delays in ingestion and have applied a fix. We'll update again when we return to real time processing.
We are still actively investigating this issue.
We are actively investigating this issue.
July 2026(12 incidents)
Error and profile ingestion issues in US
4 updates
The backlog has been cleared and ingestion is back to normal.
We have resolved the incident and are monitoring our ingestion backlog.
We have identified the issue and error and profile ingestion is back up in US. Expect delays in ingestion and alerting for errors and profiles.
We are experiencing issues with error and profile ingestion in our US region and are investigating the issue.
Delayed ingestion on us region
6 updates
We've burned through our spans backlog. Latency across span consumers are normal.
We're still burning through our spans backlog
We've found and fixed the root cause and are burning through our spans backlog. Ingestion should be back to normal in around an hour.
We are still actively investigating this issue
We are still actively investigating this issue
We are actively investigating this issue
EU Region Error, Attachment, and Feedback latency
10 updates
We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types.
We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog.
The backlog on attachments in our EU region is fully burned, and latency is back to normal. While new error events are being processed with normal latency, we have a backlog of old error events that we are now burning through.
We have implemented a fix for our attachment ingestion issue in our EU region, and are monitoring while the backlog burns. We will update here when latency is back to normal.
We have implemented a fix for errors and feedback ingestion in our EU region, and latency for those pipelines has returned to normal. We are still working on fixing our attachments ingestion pipeline in EU.
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are working on a fix.
we are investigating an issue affecting errors ingestion in the DE/EU region
Github Integration Webhook processing delay
8 updates
The webhook backlog is now resolved.
The webhook backlog is processing.
The webhook backlog is processing.
The webhook backlog is processing. Estimated recovery is now 2-2.5 hours.
The webhook backlog is processing.
The webhook backlog is processing.
The webhook backlog is being processed, ETA ~3 hours until fully caught up. Seer code reviews will run and linked Github issues and PRs will update incrementally.
The issue is mitigated and the webhook backlog is being processed. Seer code reviews will run and linked Github issues and PRs will update incrementally.
Error ingestion degraded in DE region
8 updates
Feedback ingestion is back to realtime and the backlog has been processed.
We are continuing to monitor ingestion, and a fix is being deployed to unblock feedback ingestion.
We are processing errors in realtime, and error backlogs have been processed. We're continuing to monitor the situation before restoring feedback ingestion.
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data. We are working to start allowing user feedback in DE.
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.
We have identified the problem and are working on recovery.
We continue to investigate the issue.
We are currently investigating the issue.
Ingestion delays in US
4 updates
Service has been restored.
Service has been restored and we are actively monitoring the situation
We identified the issue and restoring service.
We are investigating ingestion delays.
Ingestion delayed for spans, logs, crons in US region
4 updates
Ingestion has caught up and alerts have been restored.
We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.
We have identified the problem and are working to restore ingestion
We are currently investigating the issue.
Error ingestion degraded in US region
8 updates
We have processed the backlog.
We have processed the majority of our backlog. We are now recovering the tail of the backlog.
We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours
We expect recovery of historical data to be complete within the next 2 hours.
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.
We have identified the problem and are working on recovery. New errors are being processed in real time and we are in the process of consuming backlogged errors.
We have identified the problem and are working on a fix, ingested errors are delayed and will be processed once the fix is in place.
We are currently investigating this issue.
Incoherent number of processed logs
2 updates
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
DE items ingestion delayed
4 updates
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
Spans, logs and metrics ingestion stopped
14 updates
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
Traces, spans, logs inaccesible for query or ingestion in de and us
4 updates
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.
June 2026(6 incidents)
Ingestion and query issues for logs, spans, traces in US
12 updates
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
Delayed Span ingestion, Replay ingestion, and Issue creation in our US region
3 updates
The issue in our US region has been resolved, and ingestion latency is back to normal.
We have implemented a fix for the problem and are monitoring the situation. We are burning our US region ingestion backlog for replays, spans, and performance issues and will update here as the situation progresses.
We have identified an issue in our US region causing delayed ingestion of spans and replays, as well as delayed creation of some issue types.
Missing SDK Client Reports and Rate Limiting Outcomes
1 update
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.
Notification delivery
7 updates
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.
Users unable to login to sentry.io
4 updates
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.
Elevated errors (EU)
1 update
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.
May 2026(10 incidents)
Codereview, Autofix, and Ask Seer outage
4 updates
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
sentry.io DE Region Outage
3 updates
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.
Higher than expected latency on sentry.io
3 updates
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.
Error Ingestion Delayed in US Region
3 updates
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 alerts for transactions delayed in EU region
2 updates
Ingestion and alerting back to normal
We've put in fixes and are monitoring the situation
Ingestion and alerting delays in US
6 updates
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 delays in us
3 updates
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
Increased UI and API timeouts
5 updates
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.
Sentry.io timeouts
7 updates
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
Sentry.io intermittently unreachable
2 updates
This incident has been resolved.
We are currently investigating the issue.
April 2026(7 incidents)
Ingestion delays and intermittent query failures
4 updates
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
Application errors in Sentry [us]
3 updates
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.
Ingestion Issue in US Legacy
1 update
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.
sentry.io intermittent availability
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Span Ingestion Delayed in the EU region
4 updates
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.
SSO login broken with Chromium browser
2 updates
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.
Data ingestion and alerts delayed for US customers
2 updates
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.
📡 Tired of checking Sentry status manually?
Better Stack monitors uptime every 30 seconds and alerts you instantly when Sentry goes down.