Sentry outage on 19 October 2026
CriticalAn email when it goes down, and when it’s back.
“Sentry is down”
On 19 October, Sentry had a critical outage affecting US region customers, with the API, dashboard, US data ingestion, alerting and notification delivery (Slack, email, PagerDuty and Microsoft Teams) marked as down. The incident was open from 20:39 to 21:32 UTC, but the status page showed components in critical outage only from 20:39 to 20:53. After that, Sentry reported working through ingestion backlogs until they were processed. The status page said the cause had been identified and addressed, but did not say what it was.
Sentry’s own incident page ↗- When
- 20:40–21:33 UTC
- How long
- 53 min
- Incident open on its page
- 20:39–21:32 UTC
- Components affected
- 19
- Sentry, 30 days before
- 2 other outages
What broke when
From Sentry’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
No other well-known service reported a problem that started then.
And 100 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- API: major outage
- Dashboard: major outage
- US Ingestion - US Error Ingestion: major outage
- US Ingestion - US Transaction Ingestion: major outage
- US Ingestion - US Attachment Ingestion: major outage
- US Ingestion - US Profile Ingestion: major outage
- US Ingestion - US Replay Ingestion: major outage
- US Ingestion - US Span Ingestion: major outage
- US Ingestion - US Cron Monitoring: major outage
- US Ingestion - US Size Analysis Ingestion: major outage
- US Ingestion - US Snapshot Ingestion: major outage
- Notification Delivery - Slack: major outage
- Notification Delivery - Email: major outage
- Notification Delivery - PagerDuty: major outage
- Notification Delivery - Microsoft Teams: major outage
- Alerting - US Errors Alerting: major outage
- Alerting - US Transactions Alerting: major outage
- Alerting - US Spans Alerting: major outage
- Alerting - US Uptime Monitoring: major outage
- Fix in place, monitoring
- API: back to normal
- Dashboard: back to normal
- US Ingestion - US Error Ingestion: back to normal
- US Ingestion - US Transaction Ingestion: back to normal
- US Ingestion - US Attachment Ingestion: back to normal
- US Ingestion - US Profile Ingestion: back to normal
- US Ingestion - US Replay Ingestion: back to normal
- US Ingestion - US Span Ingestion: back to normal
- US Ingestion - US Cron Monitoring: back to normal
- US Ingestion - US Size Analysis Ingestion: back to normal
- US Ingestion - US Snapshot Ingestion: back to normal
- Notification Delivery - Slack: back to normal
- Notification Delivery - Email: back to normal
- Notification Delivery - PagerDuty: back to normal
- Notification Delivery - Microsoft Teams: back to normal
- Alerting - US Errors Alerting: back to normal
- Alerting - US Transactions Alerting: back to normal
- Alerting - US Spans Alerting: back to normal
- Alerting - US Uptime Monitoring: back to normal
- Resolved
Where this comes from
Stackpulse reads Sentry’s official status page at status.sentry.io every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with Sentry. Names and logos belong to their owners.