- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 100
What to do
Check whether your product depends on Sentry. 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 1m it lasted.
Anything that failed between 2026-09-10 15:25 UTC and 2026-09-10 16:26 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
During migration to new control silo region we started to observe increased number of 500 errors. Migration procedure was rolled back.
provider
- monitoring
Issue were identified and fixes were applied. We continue to monitor situation
provider
- resolved
Issue fully 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-0e8c49ba71
Is Sentry still down?
No, this incident was resolved 2026-09-10 16:26 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
1h 1m, from 2026-09-10 15:25 UTC to 2026-09-10 16:26 UTC, by the times Sentry posted.
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.