← Back to the carnage
SENTRY
🟠 Sentry's US region went full ostrich mode on error ingestion, now playing archaeological dig to recover 25M lost events. They keep saying '2 hours' with the confidence of a contractor giving time estimates. (Auto-resolved: no updates in 24h)
// The official story
Error ingestion degraded in US region
// Status page says
Jul 11 , 02:37 UTC Update - We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours Jul 11 , 01:46 UTC Update - We expect recovery of historical data to be complete within the next 2 hours. Jul 11 , 00:56 UTC</sma
🔗 Official status page (for the PR-approved version)
https://status.sentry.io/incidents/x19gt7qcgcwbSentry'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)