Sentry Outage History

Sentry.io experienced intermittent availability issues for 14 minutes. The service was classified as having minor impact during the outage. A fix was implemented and the incident was resolved after monitoring confirmed the solution was effective.

Sentry experienced delayed span ingestion in the EU region for 2.6 hours. The issue affected the processing and availability of tracing data for users in that region. The problem was identified and resolved with a fix that restored normal ingestion functionality.

Sentry's SSO login functionality was broken for users accessing the service through Chromium browsers, causing form submission failures due to a Content Security Policy (CSP) bug. Users were unable to log in through the normal SSO flow, though a workaround of using Cmd/Ctrl + click on the "Login with Provider" button remained available. The issue was resolved after 1.4 hours by fixing the underlying CSP bug.

Sentry experienced a 47-minute incident where US customers faced delays in data ingestion and alerts. The underlying issue was resolved and the service worked through the accumulated backlog. Normal ingestion and alert functionality was restored for all affected US customers.

Sentry experienced a data ingestion delay affecting all data types between 08:40 – 08:55 UTC on April 10, 2026. The incident impacted the platform's ability to process incoming data across all supported data types during this 15-minute window. The issue was resolved and all systems returned to normal operation by 11:44 UTC, with data ingestion functioning properly across all data types.

Sentry experienced an issue where customers were unable to access their subscription management page for 2.2 hours. The problem affected all users trying to view or manage their subscription details. The issue was resolved with a hot fix that restored full access to subscription pages.

A manual change performed on Sentry caused degraded performance and delayed ingestion across multiple pipelines including spans, crons, replays, and uptime monitoring between 13:45 and 13:52 PT. The problematic change was cancelled and normal operations were restored within 23 minutes.

Sentry experienced processing delays for errors and spans in the US region due to excessive load on their caching layer and PostgreSQL clusters. The incident affected error ingestion capabilities for 5.6 hours. The issue was resolved by identifying and mitigating the source of database load, allowing backlogs to be processed.

Sentry experienced delays in data ingestion and alert delivery for customers in the US region over a 3.5 hour period. The service team worked to process the accumulated backlog of data during the incident. The issue was resolved once all ingestion and alerts were caught up and processing normally.

Sentry experienced ingestion delays for transactions, uptime monitoring, spans, and cron jobs in the US region for 2.1 hours. The delays affected alert delivery and potentially caused some alerts for older time windows to be dropped. The team actively mitigated the issue and restored normal ingestion, with the incident fully resolved.