Live  /  Sentry  /  Incident

Sentry: EU region replay ingestion latency

Sentry · sentry.ioMinor incidentResolved2026-11-10 22:09 UTC
Public — what happened

Summary

Sentry reported a minor incident in which replay events sent to its EU region were taking longer than normal to be processed. The company said it started at 21:21 UTC on 2026-11-10, and that it had identified the problem and was working on a fix. The incident was marked resolved at 22:09 UTC the same day.

Affected

EU Replay Ingestion

As listed on Sentry’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Sentry against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Sentry: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Sentry report →

More from Sentry

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Sentry status & history page.

Related: Sentry status & history. SquidGrid is not affiliated with Sentry.