Sentry incident
Ingestion and query issues for logs, spans, traces in US
Resolved after 12 hours 43 minutes, on June 30, 2026.
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).
Update timeline
- investigating Jun 30, 2026, 09:16 PM UTC
We are currently investigating the issue
- investigating Jun 30, 2026, 09:42 PM UTC
We continue to investigate the issue. Ingestion delays are around 40 minutes now.
- investigating Jun 30, 2026, 10:50 PM UTC
We continue to investigate the issue
- investigating Jun 30, 2026, 11:31 PM UTC
We continue to investigate the issue.
- investigating Jul 01, 2026, 12:27 AM UTC
Our database is stabilized. We are attempting a fix to increase the ingestion rate.
- investigating Jul 01, 2026, 01:29 AM UTC
Our ingestion fix was not successful. We are continuing to investigate possible solutions
- investigating Jul 01, 2026, 02:25 AM UTC
We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US
- 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.
- monitoring Jul 01, 2026, 04:26 AM UTC
We continue to monitor the situation
- monitoring Jul 01, 2026, 05:22 AM UTC
We continue to monitor the situation
- 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).
- resolved Jul 01, 2026, 10:00 AM UTC
Data is now processed live and the system are fully operational.
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.
Amazon Web Services