Skip to main content
incident.io

Sentry integration degraded

Degraded Lasted 23m · started · incident.io's page

Level
confirmed
Worst impact
Degraded
Down Index
15of 100

What to do

  • Check whether your product depends on incident.io. 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 23m it lasted.

    Anything that failed between 2026-01-12 15:36 UTC and 2026-01-12 15:59 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 3

  1. identified

    We have identified increased error rates with our Sentry integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

    provider

  2. monitoring

    Sentry have acknowledged an issue on their side ([https://status.sentry.io/incidents/wpg3tnwnwctj](https://status.sentry.io/incidents/wpg3tnwnwctj "https://status.sentry.io/incidents/wpg3tnwnwctj")), and we're seeing alerts come through from them ok. We'll continue to monitor things before closing this out.

    provider

  3. resolved

    We've not seen any errors from Sentry since 15:35 UTC so we're closing this out. Please see Sentry's status page for any further details.

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

Is incident.io still down?

No, this incident was resolved 2026-01-12 15:59 UTC. For incident.io's live state, see https://down.guide/incident-io.

How long did it last?

23m, from 2026-01-12 15:36 UTC to 2026-01-12 15:59 UTC, by the times incident.io posted.

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.