- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dashboard, AuthKit
Summary
WorkOS says intermittent 503 errors affected a small fraction of requests routed through certain regions, primarily Ashburn, Virginia, due to an issue with an upstream provider. The upstream provider mitigated the issue, 503 error rates returned to normal, and the incident is now resolved.
Written by anthropic/claude-haiku-5.5 from WorkOS's own updates.
What to do
Check whether you use WorkOS Dashboard, AuthKit. 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 4h 19m it lasted.
Anything that failed between 2026-11-07 19:51 UTC and 2026-11-08 00: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 5
- identified
We're seeing intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We've isolated this to an issue with an upstream provider and are working with them on a resolution.
provider
- identified
We continue to see intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We will provide updates as they become available while we work with our upstream provider.
provider
- identified
We continue to see intermittent 503 errors on a small fraction of requests routed through Ashburn, Virginia. We continue to work with the upstream provider.
provider
- monitoring
Our upstream provider has mitigated the issue affecting those edge regions and 503 error rates have returned to normal.
provider
- resolved
This incident has been 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-cdb2d4d3c1
Is WorkOS still down?
No, this incident was resolved 2026-11-08 00:10 UTC. For WorkOS's live state, see https://down.guide/providers/workos.
How long did it last?
4h 19m, from 2026-11-07 19:51 UTC to 2026-11-08 00:10 UTC, by the times WorkOS posted.
What was affected?
WorkOS named Dashboard, AuthKit.
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.