Span & Transaction ingestion delayed in DE
All backlogs have been processed.
The latest update from Sentry.
State
Resolved
Started
80 d ago
2026-08-13 17:47 UTC
Lasted
4 h 40 min
until 2026-08-13 22:27 UTC
Worst impact
Partial outage
Timeline
10 updatesInvestigating
48 min 17%
Identified
1 h 21%
Monitoring
2 h 52 min 62%
Updates
Times in UTCAs posted by Sentry
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
Affected components
3Sentry in the last 90 days
Full historyIncidents in 90 days
23
Days with an incident
17
Median duration
2 h 12 min
This incident
2.1× the median
Other Sentry incidents
All incidentsSentry·Increased latency processing integration webhooks
We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.
Sentry·Sentry.io not loading in US region
Native events ingestion has caught up, everything should be operational now
Sentry·Sentry.io not loading
We have a mitigation in place that should prevent this from occurring again in the short term while we continue to work on a proper fix. We are going to close the Statuspage incident for now, but will reopen it if things become unstable again.
Sentry·Sentry is down
Backlogs have been processed and we are back to normal.
Sentry·Ingestion Halted for EAP data in EU
The issue with EAP ingestion in EU has been resolved.
Follow Sentry
Your coding agent knows when Sentry is down, and tells you when a failure is theirs, not yours. You can also get Sentry incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sentry" and tell me if Sentry has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=sentry/feed subscribe https://outages.cc/feed.xml?providers=sentryFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane