- Level
- confirmed
- Worst impact
- Partial outage
- WorkOS says
- 2026-10-23 15:21 to 15:50 UTC (29m)
- Components
- AuthKit, SSO
- Regions
- latam, us
- Down Index
- 35of 100
What to do
Check whether you use WorkOS AuthKit, SSO in latam, us. 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 3m it lasted.
Anything that failed between 2026-10-23 15:57 UTC and 2026-10-23 17:01 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 3
- investigating
We are seeing elevated errors and request latency across SSO and AuthKit due to network degradation and an upstream provider.
provider
- monitoring
We're seeing recovery across services and will continue to monitor.
provider
- resolved
This is now resolved. Errors and latency were elevated between 15:21 and 15:50 UTC primarily for requests served by MIA and ATL with some impact on the US east coast and northern South America.
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-db1abdf070
Is WorkOS still down?
No, this incident was resolved 2026-10-23 17:01 UTC. For WorkOS's live state, see https://down.guide/providers/workos.
How long did it last?
1h 3m, from 2026-10-23 15:57 UTC to 2026-10-23 17:01 UTC, by the times WorkOS posted.
What was affected?
WorkOS named AuthKit, SSO in latam, us.
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.