Sentry incident: Delayed Span ingestion, Replay ingestion, and Issue creation in our US region

Affected components

• US Replay Ingestion
• US Span Ingestion

1. resolvedJun 24, 2026, 20:48 UTC

   The issue in our US region has been resolved, and ingestion latency is back to normal.

2. monitoringJun 24, 2026, 19:53 UTC

   We have implemented a fix for the problem and are monitoring the situation. We are burning our US region ingestion backlog for replays, spans, and performance issues and will update here as the situation progresses.

3. identifiedJun 24, 2026, 18:52 UTC

   We have identified an issue in our US region causing delayed ingestion of spans and replays, as well as delayed creation of some issue types.

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.

• Snyk: Degraded Performance SNYK-US-01Major · Jun 22, 2026, 22:21 UTC
• Smartsheet: Increased spam activity with Smartsheet FormsMinor · Jun 18, 2026, 21:42 UTC
• Snyk: Third-Party Vendor Security Incident (Klue)Minor · Jun 19, 2026, 23:15 UTC
• 1Password: Restoring Access with a Recovery Code Is Failing for Some UsersMinor · Jun 24, 2026, 17:15 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