Skip to main content
Sentry

Ingestion delays in US and EU regions

Degraded Lasted 1h 12m · started · Sentry's page

Level
confirmed
Worst impact
Degraded
Regions
eu, us

What to do

  • Check whether you use Sentry in eu, 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 12m it lasted.

    Anything that failed between 2026-03-02 19:57 UTC and 2026-03-02 21:09 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 5

  1. investigating

    We are currently investigating this issue.

    provider

  2. identified

    The issue has been identified and the fix is being implemented.

    provider

  3. monitoring

    We have implemented a fix and are monitoring

    provider

  4. monitoring

    EU ingestion has been restored and latency is back to normal levels. US continues to recover and will likely be caught up within the next hour.

    provider

  5. resolved

    This incident has been resolved.

    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-bba7a968c0

Is Sentry still down?

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

How long did it last?

1h 12m, from 2026-03-02 19:57 UTC to 2026-03-02 21:09 UTC, by the times Sentry posted.

What was affected?

Sentry named in eu, 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.