Skip to content

Outage tracker / WorkOS

Is WorkOS down?

I'm having a problem

Operationalchecked 1 minute ago

We reached WorkOS from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured WorkOS (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East233 msOperational
US-West523 msOperational
Europe176 msOperational
Asia-Pacific518 msOperational
US-Central149 msOperational
Canada689 msOperational
UK125 msOperational
Southeast Asia448 msOperational
Australia420 msOperational
South America611 msOperational
their status pagetheir claim, not our reading

WorkOS reports: All systems operational (“All Systems Operational”)

from WorkOS's own status page, checked Sep 5, 2026, 1:45 AM UTC
Our probes and WorkOS's own status page agree: both show WorkOS as reachable right now.

WorkOS's own component breakdown, as they publish it

  • DashboardOperational
  • SSOOperational
  • Admin PortalOperational
  • Directory SyncOperational
  • Audit LogsOperational
  • AuthKitOperational
  • FGAOperational

These are WorkOS's components, named and scored by WorkOS. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is WorkOS's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

WorkOS response time, by region

US-East
270msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 974ms2026-08-23 UTC: p95 1.0s2026-08-24 UTC: p95 906ms2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 538ms2026-08-27 UTC: p95 748ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 716ms2026-08-30 UTC: p95 269ms2026-08-31 UTC: p95 260ms2026-09-01 UTC: p95 771ms2026-09-02 UTC: p95 576ms2026-09-03 UTC: p95 707ms2026-09-04 UTC: p95 526ms2026-09-05 UTC: p95 270ms
Aug 7Aug 21Sep 5
US-West
541msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 225ms2026-08-23 UTC: p95 538ms2026-08-24 UTC: p95 244ms2026-08-25 UTC: p95 360ms2026-08-26 UTC: p95 341ms2026-08-27 UTC: p95 671ms2026-08-28 UTC: p95 796ms2026-08-29 UTC: p95 638ms2026-08-30 UTC: p95 818ms2026-08-31 UTC: p95 618ms2026-09-01 UTC: p95 353ms2026-09-02 UTC: p95 596ms2026-09-03 UTC: p95 397ms2026-09-04 UTC: p95 568ms2026-09-05 UTC: p95 541ms
Aug 7Aug 21Sep 5
Europe
224msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 325ms2026-08-23 UTC: p95 460ms2026-08-24 UTC: p95 444ms2026-08-25 UTC: p95 469ms2026-08-26 UTC: p95 353ms2026-08-27 UTC: p95 337ms2026-08-28 UTC: p95 331ms2026-08-29 UTC: p95 343ms2026-08-30 UTC: p95 363ms2026-08-31 UTC: p95 338ms2026-09-01 UTC: p95 448ms2026-09-02 UTC: p95 643ms2026-09-03 UTC: p95 378ms2026-09-04 UTC: p95 335ms2026-09-05 UTC: p95 224ms
Aug 7Aug 21Sep 5
Asia-Pacific
574msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 376ms2026-08-23 UTC: p95 687ms2026-08-24 UTC: p95 582ms2026-08-25 UTC: p95 782ms2026-08-26 UTC: p95 686ms2026-08-27 UTC: p95 557ms2026-08-28 UTC: p95 595ms2026-08-29 UTC: p95 651ms2026-08-30 UTC: p95 739ms2026-08-31 UTC: p95 736ms2026-09-01 UTC: p95 666ms2026-09-02 UTC: p95 764ms2026-09-03 UTC: p95 712ms2026-09-04 UTC: p95 658ms2026-09-05 UTC: p95 574ms
Aug 7Aug 21Sep 5
US-Central
213msp95 · latest
500ms250ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 493ms2026-09-04 UTC: p95 330ms2026-09-05 UTC: p95 213ms
Aug 7Aug 21Sep 5
Canada
658msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 465ms2026-09-04 UTC: p95 438ms2026-09-05 UTC: p95 658ms
Aug 7Aug 21Sep 5
UK
262msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 324ms2026-09-04 UTC: p95 315ms2026-09-05 UTC: p95 262ms
Aug 7Aug 21Sep 5
Southeast Asia
552msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 930ms2026-09-05 UTC: p95 552ms
Aug 7Aug 21Sep 5
Australia
427msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 671ms2026-09-04 UTC: p95 791ms2026-09-05 UTC: p95 427ms
Aug 7Aug 21Sep 5
South America
662msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 992ms2026-09-04 UTC: p95 855ms2026-09-05 UTC: p95 662ms
Aug 7Aug 21Sep 5

Is it WorkOS, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not WorkOS -- it cannot diagnose WorkOS's own systems.

What we measured, function by function

WorkOS answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 233msstatus code: 401checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach WorkOS normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 523msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach WorkOS normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 149msstatus code: 401checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach WorkOS normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 689msstatus code: 401checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach WorkOS normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 611msstatus code: 401checked: Sep 5, 2026, 1:38 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach WorkOS normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 176msstatus code: 401checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach WorkOS normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 125msstatus code: 401checked: Sep 5, 2026, 1:42 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach WorkOS normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 518msstatus code: 401checked: Sep 5, 2026, 1:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach WorkOS normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 448msstatus code: 401checked: Sep 5, 2026, 1:18 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach WorkOS normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 420msstatus code: 401checked: Sep 5, 2026, 1:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach WorkOS normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using WorkOS, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for WorkOS yet, which is not evidence that nothing is wrong.

Recent outages

Static asset delivery failures, 2h 27mdeclared on their status page2026-09-02
Degraded outbound email delivery, 35mdeclared on their status page2026-08-31
Degraded Vault pages in Dashboard, 16mdeclared on their status page2026-08-27
Dashboard sign-in errors, 1h 5mdeclared on their status page2026-08-25
Elevated errors on AuthKit authentication endpoints, 1mdeclared on their status page2026-08-19
Delayed Email Deliverability, 44h 29mdeclared on their status page2026-08-15
Delayed Email Deliverability, 31mdeclared on their status page2026-08-14
Intermittent Dashboard sign-in errors, 1h 22mdeclared on their status page2026-08-11

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring WorkOS since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for WorkOS covering any window you pick, with our measurements and WorkOS's own claim at the time, side by side.

Full availability history for WorkOS: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching WorkOS, and again when they can reach it again. That is our own measurement from ten regions, not WorkOS's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

WorkOS uptime measured by RealUptimeLive, from this page's own readings.
[![WorkOS uptime measured by RealUptime](https://realuptime.io/outages/workos/badge.svg?days=30)](https://realuptime.io/outages/workos)
<a href="https://realuptime.io/outages/workos"><img src="https://realuptime.io/outages/workos/badge.svg?days=30" alt="WorkOS uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What WorkOS's SLA implies, from our measurement

At or above your target

We measured none of downtime for WorkOS over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from WorkOS's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://api.workos.com/user_management/users
secondary
https://workos.com/
secondary
https://status.workos.com/api/v2/status.json
RealUptime is not affiliated with WorkOS; the name identifies what we measured, and nothing here speaks for WorkOS's own team. We send a single web request to WorkOS from 10 regions on our own schedule and time the response. We do not see inside WorkOS's systems, do not use an account or real transaction, and are not the same signal WorkOS's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for WorkOS is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.