Sentry Outage History

Sentry experienced error ingestion delays in the US region for 2.9 hours, specifically affecting symbolicated issues while non-symbolicated issues continued processing normally. The engineering team implemented a fix and monitored the situation until ingestion returned to normal levels.

Sentry experienced delayed ingestion and alerts for transactions in the EU region for 10 minutes. The service disruption was classified as minor and affected transaction processing and alerting functionality for European users. Fixes were implemented and the situation was being monitored for stability.

Sentry experienced ingestion and alerting delays in the US region affecting spans, trace metrics, and logs for 5.6 hours. The incident was classified as minor severity and remained under investigation throughout the duration. The service delays impacted data processing and alert delivery for US-based users.

Sentry experienced ingestion and alerting delays in the US region affecting spans, transactions, and replays for 3.4 hours. The service disruption impacted data processing and notification delivery for users in the affected region. The issue was resolved and ingestion and alerting returned to steady state after monitoring confirmed normal operations.

Sentry experienced increased UI and API timeouts and errors for 10.2 hours due to an overloaded database cluster. The team applied a configuration change to mitigate the issues and fully resolved the incident. Ingestion and alerting functionality remained unaffected throughout the incident.

Sentry experienced increased UI and API timeouts and errors for 6.7 hours due to an overloaded database cluster. The incident also caused delays in ingestion for spans, replays, and crons of approximately 15 minutes, while alerting remained unaffected. The issue was resolved after implementing a fix that restored normal database performance.

Sentry.io experienced intermittent connectivity issues that prevented users from accessing the service. The outage lasted approximately 15 minutes before being resolved. The incident was classified as minor and has been fully restored.

Sentry experienced a 4.1-hour incident involving delays in their ingestion pipeline and intermittent query failures, which caused Explorer views to operate in a degraded state. The team gradually restored ingestion to normal levels and slowly increased write traffic to minimize API failures. The incident was fully resolved after a monitoring period to ensure system stability.

Sentry experienced application errors in their US region that affected API and dashboard performance, as well as causing ingestion delays for spans and replays of approximately 10 minutes. The incident lasted 11 minutes total, with API and dashboard performance recovering first, followed by the ingestion backlog catching up. All application features returned to normal operation after the brief outage.

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.