Sentry incident: Errors alerting degraded in US region

Affected components

• Alerting - US Errors Alerting

1. resolvedAug 25, 2026, 12:38 UTC

   Error alerting is back to normal.

2. identifiedAug 25, 2026, 12:27 UTC

   We have identified the issue and implemented a fix.

3. investigatingAug 25, 2026, 11:09 UTC

   We are continuing to investigate the issue

4. investigatingAug 25, 2026, 09:38 UTC

   We are investigating delays in error alerts in the US region, up to 10 minutes

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.

• DigitalOcean: Cloud Control Panel and APICritical · Aug 24, 2026, 17:14 UTC
• Shippo: Elevated error rate on Third party vendor Tracking APIMajor · Aug 25, 2026, 05:18 UTC
• Confluence: Notifications are delayedMajor · Aug 25, 2026, 08:42 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• Grafana Cloud: Incident Management unavailable in US CentralMinor · Aug 25, 2026, 10:39 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