- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 1h 57m it lasted.
Anything that failed between 2026-11-02 15:39 UTC and 2026-11-02 17:35 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
- identified
We have identified increased error rates and latency 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. Sentry's incident can be tracked on their status page here (https://status.sentry.io/incidents/35sw8wr49l3p).
provider
- monitoring
Sentry is experiencing an outage affecting their API. Alerts from Sentry are still being received. Other actions we take in Sentry, such as adding comments to linked issues or automatically resolving them, may fail or be delayed until Sentry recovers. You can follow Sentry's incident on their status page (https://status.sentry.io/incidents/35sw8wr49l3p).
provider
- resolved
We're seeing that Sentry performance has returned to normal. Sentry have reported that the issue is mitigated, but they are continuing to monitor the situation. You can follow further updates on their status page (https://status.sentry.io/incidents/35sw8wr49l3p).
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-80b03550f0
Is incident.io still down?
No, this incident was resolved 2026-11-02 17:35 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
1h 57m, from 2026-11-02 15:39 UTC to 2026-11-02 17:35 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.