- 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 2h 22m it lasted.
Anything that failed between 2026-03-13 14:19 UTC and 2026-03-13 16:40 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 4
- investigating
We are currently investigating reports that users are unable to login using Slack.
provider
- identified
Users in some Slack workspaces are unable to sign in with Slack. We have escalated this issue to Slack. Signing in with SAML and Microsoft Teams is not affected.
provider
- monitoring
Slack have rolled back a change which caused this issue, and we have confirmed recovery. Please reach out to support if you're still experiencing any issues signing in with Slack.
provider
- resolved
Slack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully.
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-4384e68941
Is incident.io still down?
No, this incident was resolved 2026-03-13 16:40 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
2h 22m, from 2026-03-13 14:19 UTC to 2026-03-13 16:40 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.