Sentry incident

Error & Span processing delays in US

Resolved after 5 hours 29 minutes, affecting US Error Ingestion and US Span Ingestion, on April 6, 2026.

monitoring Apr 06, 2026, 08:52 PM UTC

We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process.

Started
Apr 06, 2026, 03:56 PM UTC
Resolved
Apr 06, 2026, 09:26 PM UTC
Duration
5h 29m
Detected by Pingoru
Apr 06, 2026, 03:56 PM UTC

Affected components

US Error IngestionUS Span Ingestion

Update timeline

  1. investigating Apr 06, 2026, 03:56 PM UTC

    We are investigating processing delays for errors and spans in the US region

  2. identified Apr 06, 2026, 05:11 PM UTC

    We have identified the problem as a load issue in our caching layer and are working to mitigate the issue.

  3. identified Apr 06, 2026, 06:26 PM UTC

    We're continuing to mitigate load in our caching and postgres infrastructure.

  4. identified Apr 06, 2026, 07:04 PM UTC

    We are continuing to mitigate load in our postgres clusters.

  5. identified Apr 06, 2026, 08:04 PM UTC

    We are continuing to mitigate load in our postgres clusters.

  6. monitoring Apr 06, 2026, 08:52 PM UTC

    We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process.

  7. resolved Apr 06, 2026, 09:26 PM UTC

    This incident has been resolved and backlogs have been processed.

Your product runs on more than Sentry

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →