checked Oct 28, 2026 12:12 AM UTC · WorkOS's official status page
WorkOS is up and running.
All components operational
Statusfield watches WorkOS alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
6 reports published by WorkOS in the last 30 days
When WorkOS breaks, it is typically resolved in 1h 6m — median across 4 resolved incidents over 30 days.
resolvedOct 23 · 17:01 UTC
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.
Reported by WorkOS on their status page.
resolvedOct 19 · 20:21 UTC
This incident has been resolved.
Reported by WorkOS on their status page.
resolvedOct 15 · 21:51 UTC
We've resolved the issue with Radar SMS challenge verifications to China.
Reported by WorkOS on their status page.
resolvedOct 9 · 19:30 UTC
From 20:20 to 20:21 UTC on October 9, 2026 some SSO and AuthKit sign-in requests failed with HTTP 500 errors. The failures hit SSO token exchange and AuthKit authenticate requests. A database maintenance operation conflicted with live sign-in traffic. The operation self-corrected and service recovered shortly thereafter with no data loss. End users who saw an error could sign in again by retrying. We are updating the maintenance job to avoid live traffic disruption.
Reported by WorkOS on their status page.
resolvedOct 1 · 21:58 UTC
This incident has been resolved.
Reported by WorkOS on their status page.
resolvedOct 1 · 15:30 UTC
On October 1, 2026, from 11:34 to 11:40 AM EDT, our CDN provider had a network problem at its Columbus, Ohio location. Some requests to the WorkOS API (api.workos.com) and to AuthKit-hosted pages failed with HTTP 500 or 403 errors. Only requests routed through that location were affected. At the peak, about 8% of all API requests failed, including Audit Logs event ingestion, authentication and Vault decrypt calls. WorkOS systems stayed healthy the whole time and the provider fixed the problem by 11:40 AM EDT. Audit Logs event ingestion (POST /audit_logs/events) was the most affected endpoint: up to 21% of event submissions failed at the peak. Events from failed requests were not recorded. If your application did not retry them, resend any audit log events submitted between 11:34 and 11:40 AM EDT.
Reported by WorkOS on their status page.
