Skip to main content
WorkOS logo

Is WorkOS Down?

No — WorkOS is up

Reachable from all 8 checked regions

Average response time: 167ms

Last checked · checks run every 6 hours

Official status page: https://status.workos.com

WorkOS uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
187ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 62 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

62-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 40 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 31 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
141ms
DNS 18ms TCP 2ms TLS 8ms TTFB 141ms
arn
167ms
DNS 36ms TCP 1ms TLS 6ms TTFB 167ms
cdg
142ms
DNS 21ms TCP 2ms TLS 7ms TTFB 142ms
dfw
125ms
DNS 57ms TCP 1ms TLS 6ms TTFB 125ms
sin
265ms
DNS 9ms TCP 1ms TLS 9ms TTFB 265ms
sjc
172ms
DNS 74ms TCP 2ms TLS 9ms TTFB 172ms
syd
256ms
DNS 24ms TCP 1ms TLS 9ms TTFB 255ms
yyz
70ms
DNS 17ms TCP 1ms TLS 10ms TTFB 70ms

What WorkOS does

WorkOS provides the enterprise authentication features SaaS products need to sell upmarket: single sign-on against a customer's identity provider, SCIM directory sync for provisioning, audit logs, and AuthKit for hosted login. It sits directly in the sign-in path of the applications built on it, so an outage stops end users authenticating rather than degrading a background feature.

What an outage looks like

Users cannot sign in to applications that use WorkOS, and SSO redirects fail or return an error after bouncing to the identity provider. New employees are not provisioned because Directory Sync stops reading the customer's directory, and departures are not deprovisioned either. Audit log delivery pauses. The dashboard and Admin Portal will not load for administrators or their customers.

What to do about it

Check status.workos.com, which reports Core Services, SSO, Directory Sync, Audit Logs, AuthKit and FGA separately from the Dashboard and Admin Portal, so a login outage can be told apart from an administrative one. Users already signed in typically keep working sessions, so tell them not to sign out. After a Directory Sync incident, reconcile users against the directory rather than assuming it caught up.

Is it down for everyone, or just you?

If this page says WorkOS is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Okta
Okta
Auth0 (Okta)
Auth0 (Okta)
1Password
1Password
Firebase
Firebase

WorkOS outage FAQ

Can existing users stay signed in during a WorkOS outage?
Usually yes. Once a session is established your application holds it, so people already signed in tend to keep working while new sign-ins fail. The practical advice during an incident is to tell them not to sign out and not to clear cookies, because that is what converts a login outage into being locked out until the incident clears.
Is it WorkOS or the customer's identity provider?
SSO involves both and the failure looks similar from the user's side. Check status.workos.com for the SSO component, then check the customer's own provider, whether that is Okta, Entra or Google. If WorkOS reads operational and only one customer is affected, the provider or that connection's configuration is the more likely cause. The measurement above probes the WorkOS API directly.
Does Directory Sync catch up after an outage?
Treat that as something to verify rather than assume. Directory Sync is listed as its own component, and while it is down both provisioning and deprovisioning stop. The security-relevant half is deprovisioning: someone removed from the customer's directory during the window may still hold access. Reconcile the user list against the directory once the component is operational again.
Does a Dashboard outage mean my users cannot log in?
No. WorkOS lists the Dashboard and Admin Portal separately from SSO, AuthKit and Core Services. The Dashboard is where you and your customers configure connections, so it can be unavailable while authentication itself keeps working normally. Only the authentication components in that list actually sit in your users' sign-in path.
What should my application do when WorkOS is unreachable?
Fail with a clear message rather than a generic error, and never fall back to skipping authentication. A login page saying the identity provider is unreachable and suggesting they try shortly generates far fewer support tickets than a blank error. If you offer more than one sign-in method, letting users fall back to another is legitimate; weakening the check is not.

How we measure this

  • We request WorkOS's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where WorkOS publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when WorkOS goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required