- Level
- confirmed
- Worst impact
- Major outage
- Regions
- us
What to do
Check whether you use Sentry in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h it lasted.
Anything that failed between 2026-10-21 08:54 UTC and 2026-10-21 09:53 UTC may need a replay.Subscribe to Sentry's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=sentry works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
We have identified the problem, and addressed the cause of the outage.Read the postmortem
Updates from Sentry 4
- investigating
We are currently investigating an issue affecting US Sentry region
provider
- monitoring
We have identified the problem, and addressed the cause of the outage. We will continue monitoring the fix
provider
- monitoring
Native events ingestion is still delayed, we are processing the backlog of native events
provider
- resolved
Native events ingestion has caught up, everything should be operational now
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-4cd0e1936d
Is Sentry still down?
No, this incident was resolved 2026-10-21 09:53 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
1h, from 2026-10-21 08:54 UTC to 2026-10-21 09:53 UTC, by the times Sentry posted.
What was affected?
Sentry named in us.
What caused it?
Sentry wrote: "We have identified the problem, and addressed the cause of the outage." The postmortem: https://stspg.io/r52z51588y46
Where does this come from?
Sentry's official status page, https://status.sentry.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.