Live  /  Sentry  /  Incident

Sentry: Ingestion delays across all data

Sentry · sentry.ioMinor incidentResolved2026-11-04 18:41 UTC
Public — what happened

Summary

Sentry said it saw slower-than-normal processing of incoming data across all of its datasets, starting at 17:31 UTC on 2026-11-04, and rated the incident minor. By 17:46 UTC the company said it had found the source of the delays in its US region and rolled out a fix, then worked through the backlog of queued events. At 18:10 UTC it said most event types in the US were back to normal speed, while transaction events from over an hour earlier were being filled in and uptime events were still catching up. Sentry marked the incident resolved at 18:41 UTC.

Affected

US Error Ingestion, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion, US Replay Ingestion, US Span Ingestion, US Cron Monitoring, Custom Metrics (beta)

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.