Sentry Outage History
Daily status observations, past incidents, and reported issue history for Sentry.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 80% | 25 | 5 |
| July 2026 | 54.8% | 31 | 14 |
| June 2026 | 83.3% | 30 | 5 |
| May 2026 | 80% | 5 | 1 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
gocd deployment pipelines down
Started:
identified
RCA complete, mitigating now
Alert backlogs in US
Started:
monitoring
We have implemented a fix and the systems are recovering. We are monitoring to ensure that backlogs are proessed.
identified
We have identified the cause and are working to determine a mitigation. This is only affecting US right now.
investigating
We are currently investigating a delay in evaluating alerts in the US region.
Span & Transaction ingestion delayed in DE
Started:
monitoring
We continue to make progress on the spans backlog with an estimated completion time of 15 minutes.
monitoring
We're continuing to make progress on the span ingestion backlog in US.
monitoring
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.
monitoring
The problematic change has been reverted and we're processing backlogs.
monitoring
The problematic change has been reverted and we're processing backlogs.
identified
We've identified the source of latency and are reverting that change.
investigating
We are currently investigating ingestion delays for spans, transactions and alerts in DE and US
investigating
We are currently investigating ingestion delays for spans and transactions in DE and US
investigating
We are currently investigating ingestion delays for spans and transactions in DE
Error ingestion delays in US
Started:
identified
We've mitigated the source of ingestion latency and are processing the backlog.
investigating
We are currently investigating error ingestion latency in US.
Sentry API timeouts (US)
Started:
monitoring
API performance has returned to expected levels. We are continuing to monitor.
investigating
We are currently investigating reports of API timeouts for the Sentry API in our US region.
Delayed Error ingestion in our US region
Started:
monitoring
We're processing new events and alerts in realtime, and continue to process the tail of the backlog.
identified
A fix has been made and the backlog is being processed.
investigating
We've identified the root cause and are actively working on mitigation.
investigating
We are actively investigating this issue.
Spans, crons, logs ingestion delayed in US region
Started:
monitoring
Ingestion latency for spans, crons, and logs is back to normal levels.
identified
We've put a fix in place and are monitoring. We anticipate catching up to ingestion within 1 hour
investigating
We are currently investigating the issue
Delayed Error ingestion in our US region
Started:
monitoring
We're processing new events in real time, and are working through a backlog of events now.
investigating
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.
investigating
We are still actively investigating this issue.
investigating
We are actively investigating this issue.
July 2026
Error and profile ingestion issues in US
Started:
monitoring
We have resolved the incident and are monitoring our ingestion backlog.
identified
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.
investigating
We are experiencing issues with error and profile ingestion in our US region and are investigating the issue.
Delayed ingestion on us region
Started:
monitoring
We're still burning through our spans backlog
monitoring
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.
investigating
We are still actively investigating this issue
investigating
We are still actively investigating this issue
investigating
We are actively investigating this issue
EU Region Error, Attachment, and Feedback latency
Started:
monitoring
We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog.
monitoring
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.
monitoring
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
investigating
we are investigating an issue affecting errors ingestion in the DE/EU region
Github Integration Webhook processing delay
Started:
identified
The webhook backlog is processing.
identified
The webhook backlog is processing.
identified
The webhook backlog is processing. Estimated recovery is now 2-2.5 hours.
identified
The webhook backlog is processing.
identified
The webhook backlog is processing.
identified
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.
identified
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
Started:
monitoring
We are continuing to monitor ingestion, and a fix is being deployed to unblock feedback ingestion.
monitoring
We are processing errors in realtime, and error backlogs have been processed. We're continuing to monitor the situation before restoring feedback ingestion.
identified
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.
identified
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.
identified
We have identified the problem and are working on recovery.
investigating
We continue to investigate the issue.
investigating
We are currently investigating the issue.
Ingestion delays in US
Started:
monitoring
Service has been restored and we are actively monitoring the situation
identified
We identified the issue and restoring service.
investigating
We are investigating ingestion delays.
Ingestion delayed for spans, logs, crons in US region
Started:
monitoring
We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.
identified
We have identified the problem and are working to restore ingestion
investigating
We are currently investigating the issue.
Error ingestion degraded in US region
Started:
monitoring
We have processed the majority of our backlog. We are now recovering the tail of the backlog.
identified
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
identified
We expect recovery of historical data to be complete within the next 2 hours.
identified
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.
identified
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.
identified
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.
investigating
We are currently investigating this issue.
Incoherent number of processed logs
Started:
investigating
We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day
DE items ingestion delayed
Started:
monitoring
We're continuing to burn down the EU spans, logs, and metrics ingestion backlog.
monitoring
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.
monitoring
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
Started:
monitoring
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.
monitoring
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.
monitoring
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.
monitoring
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.
investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
monitoring
We're still consuming the backlog and monitoring the situation.
monitoring
Backlog is being consumed and we’re still monitoring recovery
monitoring
The issue was fixed and we are now monitoring the fix
investigating
We are investigating consumers for spans, logs and metrics are not ingested
Traces, spans, logs inaccesible for query or ingestion in de and us
Started:
monitoring
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
identified
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
investigating
We are currently investigating the issue.
June 2026
Ingestion and query issues for logs, spans, traces in US
Started:
monitoring
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).
monitoring
We continue to monitor the situation
monitoring
We continue to monitor the situation
monitoring
We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01.
investigating
We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US
investigating
Our ingestion fix was not successful. We are continuing to investigate possible solutions
investigating
Our database is stabilized. We are attempting a fix to increase the ingestion rate.
investigating
We continue to investigate the issue.
investigating
We continue to investigate the issue
investigating
We continue to investigate the issue. Ingestion delays are around 40 minutes now.
investigating
We are currently investigating the issue
Delayed Span ingestion, Replay ingestion, and Issue creation in our US region
Started:
monitoring
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.
identified
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.
Notification delivery
Started:
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.
Users unable to login to sentry.io
Started:
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.
May 2026
Codereview, Autofix, and Ask Seer outage
Started:
monitoring
The fix has been deployed and we are monitoring the situation
identified
We have identified the cause of the issue and are deploying a fix
investigating
We are currently investigating the issue
sentry.io DE Region Outage
Started:
monitoring
We have implemented a fix and are monitoring.
investigating
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 are investigating higher than expected latency
Started:
monitoring
We have implemented a fix and are monitoring.
investigating
We are currently investigating slow page loads on sentry.io.
Error Ingestion Delayed in US Region
Started:
investigating
We are implementing a fix and monitoring the situation. Non-symbolicated issues are not experiencing delays.
investigating
We are experiencing ingestion delays for errors in the US region.
Ingestion and alerts for transactions delayed in EU region
Started:
monitoring
We've put in fixes and are monitoring the situation
Ingestion and alerting delays in US
Started:
investigating
We are continuing to investigate the issue.
investigating
We are still investigating the issue.
investigating
We are still investigating the issue.
investigating
We are still investigating the issue.
investigating
We are experiencing ingestion and alerting delays in us for spans, trace metrics, and logs
Ingestion and alerting delays in us
Started:
monitoring
Ingestion and alerting are back to normal. We continue to monitor the situation
investigating
We are experiencing ingestion and alerting delays in us for spans, transactions, and replays
Increased UI and API timeouts
Started:
monitoring
We've applied a configuration change to mitigate the API/UI errors being experienced.
investigating
We are continuing to investigate increased UI and API timeouts and errors.
investigating
We are continuing to investigate increased UI and API timeouts and errors
investigating
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
Started:
monitoring
We have implemented a fix and are monitoring the situation
investigating
We are working on restoring normal service. API and application performance should be improved, ingestion still has delays.
investigating
Our event database continues to have issues and we are actively investigating the issue.
investigating
Ingestion for spans, replays, and crons is delayed by about 15 minutes.
investigating
We are continuing to investigate degraded database performance.
investigating
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
Started:
investigating
We are currently investigating the issue.
April 2026
Ingestion delays and intermittent query failures
Started:
monitoring
The system is operating as normal, we are still investigating the root cause
investigating
Ingestion is now back to normal, we are slowly increasing write traffic to reduce intermittent API failures
investigating
We are experiencing delays on our ingestion pipeline. Explorer views are in a degraded state
Application errors in Sentry [us]
Started:
monitoring
Ingestion for spans and replays is about 10 minutes behind and catching up. API and Dashboard performance has returned to normal.
investigating
We are currently investigating this issue.
sentry.io intermittent availability
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
Span Ingestion Delayed in the EU region
Started:
monitoring
The delay has recovered and we are monitoring the fix.
identified
We have identified the issue and are working on a fix.
investigating
We are currently investigating this issue.
SSO login broken with Chromium browser
Started:
identified
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
Started:
investigating
US customers may experience delay in data ingestion and alerts. The issue is resolved and we are burning the backlog.
Ingestion Delay – All Data Types
Started:
monitoring
We experienced a delay in data ingestion affecting all data types between 08:40 – 08:55 UTC.
Subcription management page not working
Started:
monitoring
We are rolling out a fix
identified
We have identified an issue for customers trying to access their subscription page. we are working on a fix
US delays and ingestion and issues in querying across pipelines
Started:
monitoring
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
Error & Span processing delays in US
Started:
monitoring
We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process.
identified
We are continuing to mitigate load in our postgres clusters.
identified
We are continuing to mitigate load in our postgres clusters.
identified
We're continuing to mitigate load in our caching and postgres infrastructure.
identified
We have identified the problem as a load issue in our caching layer and are working to mitigate the issue.
investigating
We are investigating processing delays for errors and spans in the US region
March 2026
Ingestion and alerts delayed in US
Started:
monitoring
Customers may experience some delay in ingestion and alerts. We are currently burning the backlog
Ingestion delayed for transactions, uptime, spans, crons in US
Started:
monitoring
Ingestion is back to normal, alerts may still be delayed
identified
We are actively mitigating the issue
investigating
We are currently investigating the issue. Some alerts may be dropped if they are for older time windows.