Changes / Sentry / Ingestion delayed for spans, logs, crons in US region
Sentry: Critical incident: Ingestion delayed for spans, logs, crons in US region
Summary
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.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 97%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Ingestion delayed for spans, logs, crons in US region
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-13 00:58 UTC
Before: not present
After: 2026-07-13 02:56 UTC
Before: not present
After: Alerting - US Spans Alerting, Alerting - US Uptime Monitoring, US Ingestion - US Cron Monitoring, US Ingestion - US Span Ingestion
Before: not present
After: We are currently investigating the issue.
Before: not present
After: We have identified the problem and are working to restore ingestion
Before: not present
After: We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.
Before: not present
After: Ingestion has caught up and alerts have been restored.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Ingestion delayed for spans, logs, crons in US region (this change) 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 |