Sentry incident

Ingestion and query issues for logs, spans, traces in US

Notice Resolved View vendor source →

Sentry experienced a notice incident on June 30, 2026, lasting 12h 43m. The incident has been resolved; the full update timeline is below.

Started
Jun 30, 2026, 09:16 PM UTC
Resolved
Jul 01, 2026, 10:00 AM UTC
Duration
12h 43m
Detected by Pingoru
Jun 30, 2026, 09:16 PM UTC

Update timeline

  1. investigating Jun 30, 2026, 09:16 PM UTC

    We are currently investigating the issue

  2. investigating Jun 30, 2026, 09:42 PM UTC

    We continue to investigate the issue. Ingestion delays are around 40 minutes now.

  3. investigating Jun 30, 2026, 10:50 PM UTC

    We continue to investigate the issue

  4. investigating Jun 30, 2026, 11:31 PM UTC

    We continue to investigate the issue.

  5. investigating Jul 01, 2026, 12:27 AM UTC

    Our database is stabilized. We are attempting a fix to increase the ingestion rate.

  6. investigating Jul 01, 2026, 01:29 AM UTC

    Our ingestion fix was not successful. We are continuing to investigate possible solutions

  7. investigating Jul 01, 2026, 02:25 AM UTC

    We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US

  8. monitoring Jul 01, 2026, 03:30 AM UTC

    We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01.

  9. monitoring Jul 01, 2026, 04:26 AM UTC

    We continue to monitor the situation

  10. monitoring Jul 01, 2026, 05:22 AM UTC

    We continue to monitor the situation

  11. monitoring Jul 01, 2026, 06:14 AM UTC

    We continue to monitor the fix. Ingestion is around 45 minutes behind and improving. APIs and dashboards are functioning normally (outside of data waiting to be ingested).

  12. resolved Jul 01, 2026, 10:00 AM UTC

    Data is now processed live and the system are fully operational.