← Back to the carnage
SENTRY
⚪ Sentry's UI played dead for a bit when the database decided to become a bottleneck—turns out cramming too much data into one place makes things angry. Engineers applied the ancient remedy of 'turning it off and on again' and now it's pretending nothing happened. (Auto-resolved: no updates in 24h)
// The official story
UI unavailable
// Status page says
Jan 12 , 17:56 UTC Resolved - This incident has been resolved. Jan 12 , 16:53 UTC Monitoring - Our UI has recovered from intermittent availability issues due to an increase in load on our DB, the load has recovered and the UI shouldn't experience any further issues. We're continuing to monitor. Jan 12 , 16:10 UTC Inve
🔗 Official status page (for the PR-approved version)
https://status.sentry.io/incidents/wpg3tnwnwctjSentry'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)