Sentry: Ingestion delayed for transactions, uptime, spans, crons in 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 2h 4m it lasted.
Anything that failed between 2026-03-16 20:17 UTC and 2026-03-16 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.

investigatingMar 16, 2026, 8:17 PM UTC
We are currently investigating the issue. Some alerts may be dropped if they are for older time windows.
provider
identifiedMar 16, 2026, 9:39 PM UTC
We are actively mitigating the issue
provider
monitoringMar 16, 2026, 10:11 PM UTC
Ingestion is back to normal, alerts may still be delayed
provider
resolvedMar 16, 2026, 10:21 PM UTC
The incident has been resolved
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Sentry still down?

No, this incident was resolved 2026-03-16 22:21 UTC. For Sentry's live state, see https://down.guide/sentry.

How long did it last?

2h 4m, from 2026-03-16 20:17 UTC to 2026-03-16 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.