Companies / Sentry / changes

Sentry change history

17Major incident
When (UTC)ChangeKind
Major incident: Ingestion Halted for EAP data in EU
Sentry reported a major outage halting EAP ingestion in the EU, affecting EU Span Ingestion, EU Spans Alerting and Dashboard. It started at 2026-10-14 05:46 UTC and resolved at 2026-10-14 08:20 UTC, lasting 2 h 33 min. Sentry implemented a fix and waited for ingestion lag to burn down.
Major incident
Critical incident: Sentry dashboard down
Sentry’s Dashboard was down in both US and EU regions in a critical incident starting at 2026-10-06 18:57 UTC and lasting 42 min. Sentry deployed a fix at 19:20 UTC and marked the Dashboard operational at 2026-10-06 19:40 UTC.
Major incident
Major incident: Delays in spans ingestion
Sentry reported major delays in EU spans ingestion starting 2026-09-18 10:17 UTC, listing EU Attachment Ingestion, EU Error Ingestion and EU Span Ingestion as affected components. The incident lasted 41 min and was marked resolved at 2026-09-18 10:58 UTC; the final update still described an upstream provider networking issue with mitigations underway.
Major incident
Critical incident: Delayed ingestion of errors in EU
Sentry reported critical EU ingestion delays affecting new errors, with EU alerting, Dashboard, and attachment, error and span ingestion listed as affected. The incident ran from 2026-09-18 08:36 UTC to 2026-09-18 11:57 UTC (3 h 20 min). Sentry identified an upstream-provider networking issue, implemented mitigation, and restored real-time processing for all data types.
Major incident
Major incident: Sentry.io elevated number of 500 errors
Sentry reported a major incident with elevated 500 errors affecting the API, Dashboard and listed US ingestion components from 2026-09-10 15:25 UTC to 2026-09-10 16:26 UTC, lasting 1 h 1 min. Errors appeared during migration to a new control silo region; Sentry rolled back the migration, applied fixes and confirmed full resolution.
Major incident
Major incident: Sentry requests timing out / 504's
Sentry reported a major outage affecting API, Dashboard, and Integration Pipeline, with requests timing out or returning 504s. It started at 2026-09-01 08:01 UTC and was resolved at 2026-09-01 11:21 UTC, lasting 3 h 20 min. Sentry identified the issue and rolled out a configuration change.
Major incident
Major incident: sentry.io is not available
Sentry reported a major outage affecting product and API availability, with the Dashboard and US ingestion components listed as affected. It started at 2026-08-27 09:24 UTC and was resolved at 2026-08-27 15:41 UTC, lasting 6 h 17 min; latency returned to normal.
Major incident
Major incident: Span & Transaction ingestion delayed in DE
Sentry reported major ingestion delays for spans and transactions in DE and US, with a US errors backlog also noted. The incident started at 2026-08-13 17:47 UTC and lasted 4 h 39 min, delaying ingestion of affected customer telemetry. Sentry resolved it at 2026-08-13 22:27 UTC after all backlogs were processed.
Major incident
Major incident: Error ingestion delays in US
Sentry reported a major incident affecting US Error Ingestion and US Errors Alerting from 2026-08-12 21:58 UTC to 2026-08-12 22:52 UTC, lasting 54 min. Error ingestion was delayed; Sentry mitigated the source of latency and processed the backlog before resolving the incident.
Major incident
Major incident: Delayed Error ingestion in our US region
Sentry reported a major degradation affecting US Error Ingestion and US Errors Alerting, starting 2026-08-12 11:45 UTC and resolved at 2026-08-12 14:48 UTC (3 h 2 min). Error ingestion and alerts were delayed; Sentry applied a fix and confirmed the backlog was processed.
Major incident
Critical incident: Spans, crons, logs ingestion delayed in US region
Sentry reported critical ingestion delays for spans, crons, and logs in the US region, starting 2026-08-07 16:21 UTC and resolved at 2026-08-07 17:08 UTC (47 min). A fix was in place by 16:30 UTC, and ingestion latency returned to normal by 16:48 UTC.
Major incident
Major incident: Delayed Error ingestion in our US region
Sentry reported a major delay in US Error Ingestion from 2026-08-06 08:59 UTC to 2026-08-06 11:21 UTC, lasting 2 h 21 min. A fix was applied, new events returned to real-time processing, and all backlogged events were processed by resolution.
Major incident
Critical incident: Error and profile ingestion issues in US
Sentry reported a critical US error and profile ingestion outage starting 2026-07-27 16:23 UTC, lasting 2 h 3 min and resolved at 2026-07-27 18:27 UTC. Ingestion was back up at 16:56 UTC, but ingestion and alerting delays continued; Sentry later confirmed the backlog was cleared and ingestion returned to normal.
Major incident
Critical incident: EU Region Error, Attachment, and Feedback latency
Sentry reported a critical EU-region incident causing high ingestion latency for errors, attachments, and feedback from 2026-07-20 11:11 UTC to 2026-07-20 16:57 UTC, lasting 5 h 46 min. Sentry implemented an attachment ingestion fix and cleared attachment and error backlogs; latency returned to normal across all event types.
Major incident
Critical incident: Error ingestion degraded in DE region
Sentry reported critical error-ingestion degradation in the DE region starting 2026-07-14 14:44 UTC and resolved at 2026-07-14 19:32 UTC, lasting 4 h 47 min. Error processing returned to real time and backlogs cleared; a fix was deployed to unblock feedback ingestion, which also returned to real time with its backlog processed.
Major incident
Critical incident: Ingestion delayed for spans, logs, crons in US region
Sentry reported critical ingestion delays for spans, logs and crons in the US region, affecting monitoring and alerting. The incident ran from 2026-07-13 00:58 UTC to 2026-07-13 02:56 UTC (1 h 58 min); Sentry implemented a fix and confirmed ingestion had caught up and alerts were restored.
Major incident
Critical incident: Error ingestion degraded in US region
Sentry reported critical degradation of US Error Ingestion and US Errors Alerting, delaying ingested errors from 2026-07-10 22:43 UTC to 2026-07-11 03:34 UTC (4 h 51 min). Sentry confirmed the backlog was processed at resolution; no specific cause was stated.
Major incident