- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on WorkOS. 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 51m it lasted.
Anything that failed between 2026-07-21 18:58 UTC and 2026-07-21 19:49 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 4
- investigating
We're investigating webhook delivery delays. We apologize for the inconvenience and will share an update once we have more information.
provider
- identified
We've identified the source of the latency and have implemented a fix.
provider
- monitoring
We're seeing a return to normal webhook latency and are continuing to monitor.
provider
- resolved
Webhook latency is back to normal levels. We have identified that this latency only affected a very small subset of customers.
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-cf3fce1546
Is WorkOS still down?
No, this incident was resolved 2026-07-21 19:49 UTC. For WorkOS's live state, see https://down.guide/workos.
How long did it last?
51m, from 2026-07-21 18:58 UTC to 2026-07-21 19:49 UTC, by the times WorkOS posted.
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.