Is WorkOS Down? How to Check WorkOS SSO & Auth API Status in 2026

WorkOS has become the default choice for B2B SaaS teams shipping enterprise-ready SSO, SCIM directory sync, and audit logs without building an in-house identity layer. Because WorkOS sits between your application and each customer's own identity provider, an outage can originate in three different places — your app, WorkOS itself, or the customer's IdP — which makes diagnosing "WorkOS is down" reports trickier than a typical API outage.

Whether you're seeing failed SAML assertions, stalled SCIM syncs, or 5xx errors from api.workos.com, this guide answers the key question: is WorkOS down for everyone, or is the problem upstream at a specific customer's identity provider?

How to Check if WorkOS is Down (Fastest Methods)

1. Check the Official WorkOS Status Page

WorkOS maintains a live status page at status.workos.com. It shows real-time uptime for the core API, SSO, Directory Sync, and the Admin Portal, with incident history for the past several months.

2. Test the WorkOS API Directly

A quick API test isolates whether the issue is on WorkOS's end or your integration:

curl https://api.workos.com/sso/connections \
  -H "Authorization: Bearer $WORKOS_API_KEY" \
  -o /dev/null -w "%{http_code}"

A 200 response means the WorkOS API is up. A 401 means your API key is invalid. A 5xx or connection timeout means WorkOS itself is experiencing an outage.

3. Rule Out the Customer's Identity Provider

A large share of "WorkOS down" reports are actually the customer's own IdP — Okta, Azure AD, or Google Workspace — having an outage. Since WorkOS brokers the SAML or OIDC handshake rather than owning identity itself, check the relevant IdP's status page before assuming a WorkOS-side failure.

4. Review Admin Portal Connection Logs

Log in to the WorkOS dashboard and inspect the connection logs for the affected organization. Failed SAML assertions, expired certificates, or SCIM provisioning errors usually show up here as organization-specific issues rather than a platform-wide incident.

Why Does WorkOS Go Down?

WorkOS's role as an identity broker creates failure modes that differ from a typical single-tenant API:

• Upstream Identity Provider Outages: Since WorkOS relays authentication to each customer's IdP, an Okta, Azure AD, or Google Workspace incident directly breaks SSO for any customer using that provider — even though WorkOS's own infrastructure is healthy.
• SCIM Directory Sync Provider Issues: Directory Sync depends on the customer's HR or identity system exposing a working SCIM endpoint. Misconfiguration or downtime on that side can look like a WorkOS sync failure.
• Webhook Delivery Backlogs: WorkOS delivers directory and connection events via webhooks. A backlog in event delivery can delay user provisioning updates without affecting live SSO logins.
• Certificate Expiry: SAML connections rely on signing certificates that periodically expire. An expired cert on either side produces authentication failures that are frequently mistaken for a platform outage.
• Underlying Cloud Provider Issues: Like any hosted service, WorkOS runs on cloud infrastructure that can experience regional incidents affecting API latency or availability.

WorkOS Troubleshooting Checklist

Best WorkOS Alternatives When It's Down

Conclusion: Enterprise Login Shouldn't Have a Single Point of Failure

WorkOS makes enterprise SSO dramatically easier to ship, but it also introduces a dependency chain across your app, WorkOS, and every customer's IdP. Teams that keep a manual login fallback and monitor their actual SSO flow — not just the API root — recover fastest when any link in that chain breaks.