- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 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 37m it lasted.
Anything that failed between 2026-05-14 14:08 UTC and 2026-05-14 15:45 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
- identified
We have identified increased error rates with our Slack integration. We are currently investigating how this is impacting our platform - this seems to be an issue on the Slack side, particularly around channel creation.
provider
- identified
We've confirmed the issue is relating to errors being returned by Slack. This is affecting a number of features of our integration, including: • Creating incident channels • Sending messages • Syncing Slack user groups Our web dashboard continues to be available and Scribe is unaffected.
provider
- monitoring
Slack have acknowledged the incident on their side. You can follow their status page here (https://slack-status.com/2026-05/fe557ca05fdb64fa).
provider
- monitoring
We're continuing to monitor the situation - Slack have posted an update on their status page to confirm that they're working on it.
provider
- resolved
The issue has been resolved on Slack's side and we've confirmed that things look normal on our side too.
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-21ebf9a842
Is incident.io still down?
No, this incident was resolved 2026-05-14 15:45 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
1h 37m, from 2026-05-14 14:08 UTC to 2026-05-14 15:45 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.