- Level
- confirmed
- Worst impact
- Degraded
- 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 2h 38m it lasted.
Anything that failed between 2026-03-09 17:59 UTC and 2026-03-09 20:37 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.
Updates from Sentry 3
- identified
US customers may experience delay in alerts. We've identified the issue and will be putting in a fix.
provider
- monitoring
We are burning the backlog and actively monitoring the progress.
provider
- resolved
Ingestion and alert latency is back to normal.
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-2d0bd7029e
Is Sentry still down?
No, this incident was resolved 2026-03-09 20:37 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
2h 38m, from 2026-03-09 17:59 UTC to 2026-03-09 20:37 UTC, by the times Sentry posted.
What was affected?
Sentry named in us.
What caused it?
Sentry hasn't published a root cause. If it does, it shows here.
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.