Sentry reported this critical-impact incident on its official status page on Jul 20, 2026, 11:11 UTC. It was resolved after 5h 46m.
Right now Sentry is operational. Live Sentry status →
We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types.
We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog.
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.
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.
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.
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.
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.
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.
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.
we are investigating an issue affecting errors ingestion in the DE/EU region
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