- 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 14m it lasted.
Anything that failed between 2026-10-02 22:33 UTC and 2026-10-02 23:47 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
Some customers on Slack Enterprise Grid who sign in with Slack are seeing Slack-originating errors when logging in. We've raised this with Slack and are monitoring for a fix. Customers using SAML sign-in aren't affected. Alert ingestion and our On-call product's paging functionality are unaffected.
provider
- resolved
This incident has been resolved. Login via Slack is operating normally again, and no further action is required.
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-8f68ac6845
Is incident.io still down?
No, this incident was resolved 2026-10-02 23:47 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
1h 14m, from 2026-10-02 22:33 UTC to 2026-10-02 23:47 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.