Skip to main content
Sentry

Error & Span processing delays in US

Degraded Lasted 5h 30m · started · Sentry's page

Level
confirmed
Worst impact
Degraded
Components
US Error Ingestion, US Span Ingestion
Regions
us

What to do

  • Check whether you use Sentry US Error 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 5h 30m it lasted.

    Anything that failed between 2026-04-06 15:56 UTC and 2026-04-06 21:26 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 7

  1. investigating

    We are investigating processing delays for errors and spans in the US region

    provider

  2. identified

    We have identified the problem as a load issue in our caching layer and are working to mitigate the issue.

    provider

  3. identified

    We're continuing to mitigate load in our caching and postgres infrastructure.

    provider

  4. identified

    We are continuing to mitigate load in our postgres clusters.

    provider

  5. identified

    We are continuing to mitigate load in our postgres clusters.

    provider

  6. monitoring

    We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process.

    provider

  7. resolved

    This incident has been resolved and backlogs have been processed.

    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-75b56f820d

Is Sentry still down?

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

How long did it last?

5h 30m, from 2026-04-06 15:56 UTC to 2026-04-06 21:26 UTC, by the times Sentry posted.

What was affected?

Sentry named US Error 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.