- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 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 7m it lasted.
Anything that failed between 2026-03-12 13:20 UTC and 2026-03-12 14:27 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 2
- identified
We've identified a drop in inbound traffic to [incident.io](http://incident.io "incident.io") from Opsgenie. This means that alerts may be slow to show up in [incident.io](http://incident.io "incident.io"), and paging via Opsgenie may be slow to reflect updates. This appears to be an issue with outbound webhooks on Opsgenie's side, we're monitoring the situation and will update as we know more.
provider
- resolved
Traffic appears to be back to normal levels now.
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-619a3acd79
Is incident.io still down?
No, this incident was resolved 2026-03-12 14:27 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
1h 7m, from 2026-03-12 13:20 UTC to 2026-03-12 14:27 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.