- Level
- confirmed
- Worst impact
- Degraded
- Components
- Directory Sync
- Down Index
- 22of 100
What to do
Check whether you use WorkOS Directory Sync. 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 17m it lasted.
Anything that failed between 2026-04-16 20:54 UTC and 2026-04-16 23:10 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’re currently investigating an elevated rate of HTTP 429 (Too Many Requests) responses impacting the /directory_users endpoint. Mitigations are in progress, and we’ll provide an update shortly.
provider
- monitoring
We’ve deployed a fix and are seeing early signs of recovery, with 429 error rates beginning to decline. We’re continuing to monitor closely to ensure the endpoint fully stabilizes and will provide further updates as needed.
provider
- resolved
The issue has been resolved. 429 error rates have returned to normal levels for the affected endpoint.
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-ebbecec0ca
Is WorkOS still down?
No, this incident was resolved 2026-04-16 23:10 UTC. For WorkOS's live state, see https://down.guide/workos.
How long did it last?
2h 17m, from 2026-04-16 20:54 UTC to 2026-04-16 23:10 UTC, by the times WorkOS posted.
What was affected?
WorkOS named Directory Sync.
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.