- Level
- confirmed
- Worst impact
- Degraded
- Components
- SSO
- Down Index
- 13of 100
What to do
Check whether you use WorkOS SSO. 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 2m it lasted.
Anything that failed between 2026-05-14 15:10 UTC and 2026-05-14 15:12 UTC may need a replay.Subscribe to WorkOS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=workos works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from WorkOS 2
- monitoring
We experienced errors in our OIDC connections. The issue is now resolved.
provider
- resolved
This issue is now resolved.
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-b6f4f94248
Is WorkOS still down?
No, this incident was resolved 2026-05-14 15:12 UTC. For WorkOS's live state, see https://down.guide/workos.
How long did it last?
2m, from 2026-05-14 15:10 UTC to 2026-05-14 15:12 UTC, by the times WorkOS posted.
What was affected?
WorkOS named SSO.
What caused it?
WorkOS hasn't published a root cause. If it does, it shows here.
Where does this come from?
WorkOS's official status page, https://status.workos.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.