- Level
- confirmed
- Worst impact
- Degraded
- Components
- US Replay Ingestion, US Span Ingestion
- Regions
- us
What to do
Check whether you use Sentry US Replay Ingestion, US Span Ingestion 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 1h 56m it lasted.
Anything that failed between 2026-06-24 18:52 UTC and 2026-06-24 20:48 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
We have identified an issue in our US region causing delayed ingestion of spans and replays, as well as delayed creation of some issue types.
provider
- monitoring
We have implemented a fix for the problem and are monitoring the situation. We are burning our US region ingestion backlog for replays, spans, and performance issues and will update here as the situation progresses.
provider
- resolved
The issue in our US region has been resolved, and ingestion 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-f044117600
Is Sentry still down?
No, this incident was resolved 2026-06-24 20:48 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
1h 56m, from 2026-06-24 18:52 UTC to 2026-06-24 20:48 UTC, by the times Sentry posted.
What was affected?
Sentry named US Replay Ingestion, US Span Ingestion 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.