- 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 21m it lasted.
Anything that failed between 2026-04-07 21:02 UTC and 2026-04-07 21:23 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 2
- monitoring
We performed a manual change that caused degraded performance and delayed ingestion in spans, crons, replays, and uptime that caused issues between 13:45 and 13:52 PT. The change has been cancelled and operations have returned to normal
provider
- resolved
This incident has been resolved
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-97c4765759
Is Sentry still down?
No, this incident was resolved 2026-04-07 21:23 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
21m, from 2026-04-07 21:02 UTC to 2026-04-07 21:23 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.