- Level
- confirmed
- Worst impact
- Degraded
- Components
- US Error Ingestion, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion, US Replay Ingestion, US Span Ingestion, US Cron Monitoring, Custom Metrics (beta)
- Regions
- us
- Down Index
- 22of 100
What to do
Check whether you use Sentry US Error Ingestion, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion and 4 more 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 10m it lasted.
Anything that failed between 2026-11-04 17:31 UTC and 2026-11-04 18:41 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
- monitoring
We are monitoring an issue involving increased ingestion latency across all our datasets.
provider
- monitoring
We have identified the issue causing ingestion delays in our US region, and have deployed a fix. We are monitoring the fix while we burn our event backlog.
provider
- monitoring
We are backfilling transaction events ingested received >1 hour ago, and still burning our backlog for uptime events in US. All other event types in our US region are being ingested with normal latency.
provider
- resolved
The issue causing ingestion delays in our US region has been resolved, all data has been backfilled and latency has returned 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-3179ea32cb
Is Sentry still down?
No, this incident was resolved 2026-11-04 18:41 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
1h 10m, from 2026-11-04 17:31 UTC to 2026-11-04 18:41 UTC, by the times Sentry posted.
What was affected?
Sentry named US Error Ingestion, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion and 4 more 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.