Skip to main content
incident.io

Increased rate of disconnections from Sentry

Degraded Lasted 3h 28m · started · incident.io's page

Level
confirmed
Worst impact
Degraded
Regions
us
Down Index
24of 100

What to do

  • Check whether you use incident.io 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 3h 28m it lasted.

    Anything that failed between 2025-12-22 10:29 UTC and 2025-12-22 13:57 UTC may need a replay.
  • Subscribe to incident.io's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=incident-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from incident.io 5

  1. identified

    We have identified an increased rate of Sentry integrations becoming disconnected. Alert ingestion is unaffected. Please don't uninstall our application from Sentry: we are working to restore these connections on our side, and no action is currently required. We will provide an update in 30 minutes.

    provider

  2. identified

    We're currently testing the fix that will allow us to re-connect any disconnected Sentry integrations on behalf of customers, and will have another update on this in 30 minutes.

    provider

  3. identified

    We've verified a fix locally, and we're starting to roll this out in production now.

    provider

  4. monitoring

    We have confirmed that we are able to restore these connections, and we are now in the process of restoring these. When this happens, you'll see that the Sentry integration no longer flags up as requiring reconnection. Once we have finished restoring access, we'll post another update here.

    provider

  5. resolved

    We have managed to re-establish a connection to Sentry for almost all of the affected customers. If Sentry is still showing up as disconnected, you will need to remove the incident.io integration from the Sentry side, and then go through the reinstallation flow by opening incident.io and going to Settings → Integrations → Sentry. If you do this, please note that Sentry will remove the "Notify incident.io" action from alert rules when you uninstall the integration. If that was the only action in the alert rule, the entire rule is disabled. You will therefore need to verify any alert rules after re-installing.

    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-66050d3219

Is incident.io still down?

No, this incident was resolved 2025-12-22 13:57 UTC. For incident.io's live state, see https://down.guide/incident-io.

How long did it last?

3h 28m, from 2025-12-22 10:29 UTC to 2025-12-22 13:57 UTC, by the times incident.io posted.

What was affected?

incident.io named in us.

What caused it?

incident.io hasn't published a root cause. If it does, it shows here.

Where does this come from?

incident.io's official status page, https://status.incident.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.