Sentry outage: Ingestion delayed for spans, logs, crons in US region

Affected components

• Alerting - US Spans Alerting
• Alerting - US Uptime Monitoring
• US Ingestion - US Cron Monitoring
• US Ingestion - US Span Ingestion

1. resolvedJul 13, 2026, 02:56 UTC

   Ingestion has caught up and alerts have been restored.

2. monitoringJul 13, 2026, 02:01 UTC

   We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.

3. identifiedJul 13, 2026, 01:46 UTC

   We have identified the problem and are working to restore ingestion

4. investigatingJul 13, 2026, 00:58 UTC

   We are currently investigating the issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Sentry's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Inngest: Issues Affecting Function Triggering from EventsMajor · Jul 10, 2026, 17:44 UTC
• Clerk: Elevated errors while configuring domainsMajor · Jul 12, 2026, 22:05 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Pinecone: [Serverless][AWS][us-east-1] Increase in freshness lag for some namespacesMinor · Jul 12, 2026, 23:21 UTC

How often does Sentry have incidents?

Sentry reported 25 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 3h. See Sentry's uptime and incident history