Sentry reported this critical-impact incident on its official status page on Jul 10, 2026, 22:43 UTC. It was resolved after 4h 51m.
Right now Sentry is operational. Live Sentry status →
We have processed the backlog.
We have processed the majority of our backlog. We are now recovering the tail of the backlog.
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
We expect recovery of historical data to be complete within the next 2 hours.
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.
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.
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.
We are currently investigating this issue.
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