Sentry incident

Error & Span processing delays in US

Minor Resolved View vendor source →

Sentry experienced a minor incident on April 6, 2026, lasting 5h 30m. The incident has been resolved; the full update timeline is below.

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

Update timeline

  1. monitoring Apr 06, 2026, 09:26 PM UTC

    Apr 6, 21:26 UTC Resolved - This incident has been resolved and backlogs have been processed. Apr 6, 20:52 UTC Monitoring - We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process. Apr 6, 20:04 UTC Update - We are continuing to mitigate load in our postgres clusters. Apr 6, 19:04 UTC Update - We are continuing to mitigate load in our postgres clusters. Apr 6, 18:26 UTC Update - We're continuing to mitigate load in our caching and postgres infrastructure. Apr 6, 17:11 UTC Identified - We have identified the problem as a load issue in our caching layer and are working to mitigate the issue. Apr 6, 15:56 UTC Investigating - We are investigating processing delays for errors and spans in the US region