Looking for an update now? Check the current status, or follow Sentry for future changes.
85.4%of 48 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
89.7%
29
3
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.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We have put a fix into place and are monitoring the situation
monitoring
We have put a fix into place and are monitoring the situation
identified
We have identified a potential cause of excess traffic and are working on a fix.
investigating
We are experiencing slower page loads and API responses due to a database issue in us
Legacy Incident Archive
46 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Delayed ingestion on us region
minorSource not attested
Last archived state: resolved
View archived record details
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
criticalSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
criticalSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
criticalSource not attested
Last archived state: resolved
View archived record details
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
criticalSource not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day
DE items ingestion delayed
Source not attested
Last archived state: resolved
View archived record details
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
Traces, spans, logs inaccesible for query or ingestion in de and us
Source not attested
Last archived state: resolved
View archived record details
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
