Skip to main content
incident.io

Issue with Slack integration

Degraded Lasted 7h 47m · started · incident.io's page

Level
confirmed
Worst impact
Degraded
Down Index
22of 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 7h 47m it lasted.

    Anything that failed between 2026-05-27 22:42 UTC and 2026-05-28 06:29 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 6

  1. 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 and message delivery.

    provider

  2. identified

    Slack have acknowledged the incident on their side. You can follow their status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).

    provider

  3. monitoring

    Error rates and latency on Slack operations have returned to normal, and the integration has recovered. You can follow updates on Slack's status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).

    provider

  4. monitoring

    We are continuing to monitor Slack as it continues to recover, and are no longer seeing any direct impact on our Slack app You can follow updates on Slack's status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f "here").

    provider

  5. monitoring

    We are continuing to monitor Slack as it recovers. We are not seeing any direct impact on our Slack app. You can follow updates on Slack’s status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f "here").

    provider

  6. resolved

    Slack have confirmed their services have largely returned to operational levels. We've not seen any direct impact on our Slack app since ~23:20 UTC yesterday. We're resolving this on our side, and you can follow any further updates on Slack’s status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).

    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-0f6f8ca97c

Is incident.io still down?

No, this incident was resolved 2026-05-28 06:29 UTC. For incident.io's live state, see https://down.guide/incident-io.

How long did it last?

7h 47m, from 2026-05-27 22:42 UTC to 2026-05-28 06:29 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.