Live  /  Sentry  /  Incident

Sentry: Delays in spans and transactions processing

Sentry · sentry.ioMajor incidentResolved2026-11-03 17:25 UTC
Public — what happened

Summary

Sentry reported a major incident that delayed the processing of spans and transactions, which are performance data collected from customers' applications. The company said the problem began at 15:40 UTC on 2026-11-03, affected only ingestion in the US and not the EU, and that no data had been lost. Sentry said it had identified the issue by 15:53 UTC and was rolling out a fix, and the incident was marked resolved at 17:25 UTC.

Affected

US Transaction Ingestion, US Span 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 46, 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.