← Back to the carnage
SENTRY
🔴 Sentry's logs, spans, and traces decided to go dark in the US. Engineering is "burning down the backlog" — which is corporate speak for "we broke it real good." ETA on recovery: sometime next year if we're lucky. (Auto-resolved: no updates in 24h)
// The official story
Ingestion and query issues for logs, spans, traces in US
// Status page says
Jul 1 , 03:30 UTC Monitoring - We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01. Jul 1 , 02:25 UTC Update - We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US Jul 1 , 01:29 UTC Update -
🔗 Official status page (for the PR-approved version)
https://status.sentry.io/incidents/4bnv32fjbj4qSentry's Greatest Hits
🟢 SENTRY
Oct 06, 2026
🟡 Sentry's dashboard went blind in both US and EU regions. The irony of an error tracking platform becoming untrackable is *chef's kiss*. Engineers are investigating whether they need to file a bug report against themselves. (Auto-resolved: no updates in 24h)
🟢 SENTRY
Sep 01, 2026
🟠 Sentry's US span ingestion decided to move at geological timescales. Engineers deployed what they're calling a 'fix'—latency is 'coming down' from 'catastrophic' to merely 'disappointing.' Your error tracking is now slower at tracking errors than the errors themselves. (Auto-resolved: no updates in 24h)
🟢 SENTRY
Aug 18, 2026
🟠 Sentry's GoCD pipelines went full Rip Van Winkle while engineers performed emergency root cause archaeology. The mitigations are supposedly in progress, which in incident speak means they found the smoking gun but haven't figured out how to put it back together yet. (Auto-resolved: no updates in 24h)
🟢 SENTRY
Jul 20, 2026
🟡 Sentry's error ingestion in DE/EU went dark—turns out the error tracker became the error. Engineers are frantically checking logs to see what logs they missed. The irony is so thick you could parse it as JSON. (Auto-resolved: no updates in 24h)