- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 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 15m it lasted.
Anything that failed between 2026-04-27 23:58 UTC and 2026-04-28 00:14 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
- monitoring
We’re seeing delays of up to 30 minutes in receiving webhooks from Opsgenie, which may delay alert delivery. Our systems are operating normally and process alerts as soon as they arrive; the issue appears to be on Opsgenie’s side. We’re monitoring closely and will share updates as we learn more.
provider
- resolved
Webhooks appear to arriving as normal again, so you should no longer see any delays.
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-a4b77c18b2
Is incident.io still down?
No, this incident was resolved 2026-04-28 00:14 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
15m, from 2026-04-27 23:58 UTC to 2026-04-28 00:14 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.