Skip to main content
Sentry

Ingestion delays and intermittent query failures

Degraded Lasted 4h 8m · started · Sentry's page

Level
confirmed
Worst impact
Degraded
Down Index
21of 100

What to do

  • Check whether your product depends on Sentry. 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 4h 8m it lasted.

    Anything that failed between 2026-04-27 16:52 UTC and 2026-04-27 20:59 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

  1. investigating

    We are experiencing delays on our ingestion pipeline. Explorer views are in a degraded state

    provider

  2. investigating

    Ingestion is now back to normal, we are slowly increasing write traffic to reduce intermittent API failures

    provider

  3. monitoring

    The system is operating as normal, we are monitoring the fix.

    provider

  4. 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-763b40acc5

Is Sentry still down?

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

How long did it last?

4h 8m, from 2026-04-27 16:52 UTC to 2026-04-27 20:59 UTC, by the times Sentry posted.

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.