Sentry reported this major-impact incident on its official status page on Aug 13, 2026, 17:47 UTC. It was resolved after 4h 40m.
Right now Sentry is operational. Live Sentry status →
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
Our 5-minute checks didn't record a change in Sentry's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Sentry reported 25 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 3h. See Sentry's uptime and incident history