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.
April 2026
Ingestion Delay – All Data Types
Source not attested
Last archived state: resolved
View archived record details
monitoring
We experienced a delay in data ingestion affecting all data types between 08:40 – 08:55 UTC.
Subcription management page not working
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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.
