Skip to main content
Sentry

Increased latency processing integration webhooks

Degraded Lasted 21m · started · Sentry's page

Level
confirmed
Worst impact
Degraded
Components
Slack, Integration Pipeline
Down Index
16of 100

What to do

  • Check whether you use Sentry Slack, Integration Pipeline. 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 21m it lasted.

    Anything that failed between 2026-10-21 17:53 UTC and 2026-10-21 18:14 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 2

  1. investigating

    We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.

    provider

  2. resolved

    We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.

    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-89940cfa20

Is Sentry still down?

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

How long did it last?

21m, from 2026-10-21 17:53 UTC to 2026-10-21 18:14 UTC, by the times Sentry posted.

What was affected?

Sentry named Slack, Integration Pipeline.

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.