- 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 5h 29m it lasted.
Anything that failed between 2026-05-18 01:41 UTC and 2026-05-18 07:11 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 6
- investigating
We are experiencing ingestion and alerting delays in us for spans, trace metrics, and logs
provider
- investigating
We are still investigating the issue.
provider
- investigating
We are still investigating the issue.
provider
- investigating
We are still investigating the issue.
provider
- investigating
We are continuing to investigate the issue.
provider
- resolved
We have implemented a fix. Ingestion and alerting have returned to normal operation
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-1a6439c6ca
Is Sentry still down?
No, this incident was resolved 2026-05-18 07:11 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
5h 29m, from 2026-05-18 01:41 UTC to 2026-05-18 07:11 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.