- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 41of 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-07-16 08:32 UTC and 2026-07-16 10:54 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
- investigating
We're aware of issues affecting some customers logging in using SAML - we're investigating and will provide an update shortly.
provider
- identified
This issue remains ongoing and we're working on a resolution. All other functionality is unaffected. Existing sessions on the mobile app and dashboard are unaffected and continue to have access as normal. We'll post our next update in the next 30 minutes.
provider
- monitoring
SAML logins are now working with increased latency. We'll continue to monitor until fully recovered. All other functionality remains unaffected.
provider
- monitoring
We're continuing to see elevated errors and latency with SAML logins. All other functionality remains unaffected.
provider
- monitoring
SAML logins are now performing as normal. We'll continue to monitor for any further issues.
provider
- resolved
SAML login has continued to perform as normal.
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-465b7994f9
Is incident.io still down?
No, this incident was resolved 2026-07-16 10:54 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
2h 22m, from 2026-07-16 08:32 UTC to 2026-07-16 10:54 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.