Sentry: Span Ingestion Delayed in the EU region

What to do

Check whether you use Sentry in eu. 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 32m it lasted.
Anything that failed between 2026-04-16 13:36 UTC and 2026-04-16 16:08 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.

investigatingApr 16, 2026, 1:36 PM UTC
We are currently investigating this issue.
provider
identifiedApr 16, 2026, 2:30 PM UTC
We have identified the issue and are working on a fix.
provider
monitoringApr 16, 2026, 3:05 PM UTC
The delay has recovered and we are monitoring the fix.
provider
resolvedApr 16, 2026, 4:08 PM UTC
The fix has been rolled out and ingestion is recovered.
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-04-16 16:08 UTC. For Sentry's live state, see https://down.guide/sentry.

How long did it last?

2h 32m, from 2026-04-16 13:36 UTC to 2026-04-16 16:08 UTC, by the times Sentry posted.

What was affected?

Sentry named in eu.

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.