WorkOS: Radar SMS challenge failures for phone numbers in mainland China (+86)

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 34m it lasted.
Anything that failed between 2026-10-15 17:17 UTC and 2026-10-15 21:51 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.

investigatingOct 15, 2026, 5:17 PM UTC
We are investigating an issue affecting Radar SMS challenge verification for phone numbers in mainland China (+86). Affected users may not receive verification codes or may encounter an error when requesting one, preventing them from completing verification. We will provide an update as more information becomes available.
provider
monitoringOct 15, 2026, 5:55 PM UTC
We are seeing some recovery after our upstream provider has enabled alternate delivery routes. We are continuing to monitor.
provider
resolvedOct 15, 2026, 9:51 PM UTC
We've resolved the issue with Radar SMS challenge verifications to China.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is WorkOS still down?

No, this incident was resolved 2026-10-15 21:51 UTC. For WorkOS's live state, see https://down.guide/workos.

How long did it last?

4h 34m, from 2026-10-15 17:17 UTC to 2026-10-15 21:51 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.