- 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 39m it lasted.
Anything that failed between 2026-08-18 21:42 UTC and 2026-08-18 22:21 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 4
- investigating
We are currently investigating a delay in evaluating alerts in the US region.
provider
- identified
We have identified the cause and are working to determine a mitigation. This is only affecting US right now.
provider
- monitoring
We have implemented a fix and the systems are recovering. We are monitoring to ensure that backlogs are proessed.
provider
- resolved
The problem has been resolved, all backlogs have cleared and everything is operational again.
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-188b1f007e
Is Sentry still down?
No, this incident was resolved 2026-08-18 22:21 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
39m, from 2026-08-18 21:42 UTC to 2026-08-18 22:21 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.