Live / Sentry / Incident
Sentry: Ingestion Halted for EAP data in EU
Sentry · sentry.ioMajor incidentResolved2026-10-14 08:20 UTC
Public — what happened
Summary
Sentry reported a major problem on October 14, 2026, starting at 05:46 UTC, in which incoming EAP data for its EU region stopped being processed. The company said it had pinpointed the issue but did not publicly describe a cause. By 06:09 UTC Sentry said a fix was in place and it was waiting for the backlog of delayed data to clear, and it moved to monitoring at 07:46 UTC. The incident was marked resolved at 08:20.
Affected
EU Span Ingestion, EU Spans Alerting
Timeline
- Started — 2026-10-14 05:46 UTC
- Identified — 2026-10-14 05:46 UTC (2 updates)
- Monitoring — 2026-10-14 07:46 UTC
- Resolved — 2026-10-14 08:20 UTC · 2h 34m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 43, 2026, our weekly internet health report.