Skip to content

Outage tracker / WorkOS

Is WorkOS down?

I'm having a problem

Operationalchecked 9 minutes ago

We reached WorkOS from all 10 regions we check.

As of Oct 5, 2026, 8:07 PM UTC, WorkOS answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:07 PM UTC
US-East317 msOperational
US-West413 msOperational
Europe279 msOperational
Asia-Pacific262 msOperational
US-Central156 msOperational
Canada95 msOperational
UK227 msOperational
Southeast Asia395 msOperational
Australia571 msOperational
South America170 msOperational
their status pagetheir claim, not our reading

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

from WorkOS's own status page, checked Oct 5, 2026, 7:52 PM 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
297msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 406ms2026-09-07 UTC: p95 379ms2026-09-08 UTC: p95 453ms2026-09-09 UTC: p95 385ms2026-09-10 UTC: p95 357ms2026-09-11 UTC: p95 393ms2026-09-12 UTC: p95 419ms2026-09-13 UTC: p95 334ms2026-09-14 UTC: p95 292ms2026-09-15 UTC: p95 182ms2026-09-16 UTC: p95 104ms2026-09-17 UTC: p95 181ms2026-09-18 UTC: p95 126ms2026-09-19 UTC: p95 137ms2026-09-20 UTC: p95 152ms2026-09-21 UTC: p95 112ms2026-09-22 UTC: p95 94ms2026-09-23 UTC: p95 271ms2026-09-24 UTC: p95 329ms2026-09-25 UTC: p95 310ms2026-09-26 UTC: p95 350ms2026-09-27 UTC: p95 442ms2026-09-28 UTC: p95 559ms2026-09-29 UTC: p95 685ms2026-09-30 UTC: p95 434ms2026-10-01 UTC: p95 412ms2026-10-02 UTC: p95 256ms2026-10-03 UTC: p95 274ms2026-10-04 UTC: p95 320ms2026-10-05 UTC: p95 297ms
Sep 6Sep 20Oct 5
US-West
420msp95 · 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-09-06 UTC: p95 475ms2026-09-07 UTC: p95 428ms2026-09-08 UTC: p95 566ms2026-09-09 UTC: p95 450ms2026-09-10 UTC: p95 312ms2026-09-11 UTC: p95 425ms2026-09-12 UTC: p95 378ms2026-09-13 UTC: p95 479ms2026-09-14 UTC: p95 492ms2026-09-15 UTC: p95 239ms2026-09-16 UTC: p95 199ms2026-09-17 UTC: p95 225ms2026-09-18 UTC: p95 220ms2026-09-19 UTC: p95 197ms2026-09-20 UTC: p95 196ms2026-09-21 UTC: p95 254ms2026-09-22 UTC: p95 254ms2026-09-23 UTC: p95 316ms2026-09-24 UTC: p95 445ms2026-09-25 UTC: p95 596ms2026-09-26 UTC: p95 463ms2026-09-27 UTC: p95 304ms2026-09-28 UTC: p95 385ms2026-09-29 UTC: p95 455ms2026-09-30 UTC: p95 507ms2026-10-01 UTC: p95 382ms2026-10-02 UTC: p95 489ms2026-10-03 UTC: p95 414ms2026-10-04 UTC: p95 423ms2026-10-05 UTC: p95 420ms
Sep 6Sep 20Oct 5
Europe
358msp95 · 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-09-06 UTC: p95 599ms2026-09-07 UTC: p95 519ms2026-09-08 UTC: p95 506ms2026-09-09 UTC: p95 513ms2026-09-10 UTC: p95 290ms2026-09-11 UTC: p95 274ms2026-09-12 UTC: p95 422ms2026-09-13 UTC: p95 539ms2026-09-14 UTC: p95 516ms2026-09-15 UTC: p95 252ms2026-09-16 UTC: p95 256ms2026-09-17 UTC: p95 270ms2026-09-18 UTC: p95 285ms2026-09-19 UTC: p95 254ms2026-09-20 UTC: p95 260ms2026-09-21 UTC: p95 281ms2026-09-22 UTC: p95 267ms2026-09-23 UTC: p95 536ms2026-09-24 UTC: p95 601ms2026-09-25 UTC: p95 581ms2026-09-26 UTC: p95 617ms2026-09-27 UTC: p95 588ms2026-09-28 UTC: p95 541ms2026-09-29 UTC: p95 652ms2026-09-30 UTC: p95 744ms2026-10-01 UTC: p95 770ms2026-10-02 UTC: p95 282ms2026-10-03 UTC: p95 296ms2026-10-04 UTC: p95 351ms2026-10-05 UTC: p95 358ms
Sep 6Sep 20Oct 5
Asia-Pacific
529msp95 · 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-09-06 UTC: p95 598ms2026-09-07 UTC: p95 438ms2026-09-08 UTC: p95 484ms2026-09-09 UTC: p95 423ms2026-09-10 UTC: p95 399ms2026-09-11 UTC: p95 582ms2026-09-12 UTC: p95 940ms2026-09-13 UTC: p95 457ms2026-09-14 UTC: p95 473ms2026-09-15 UTC: p95 345ms2026-09-16 UTC: p95 456ms2026-09-17 UTC: p95 291ms2026-09-18 UTC: p95 289ms2026-09-19 UTC: p95 509ms2026-09-20 UTC: p95 343ms2026-09-21 UTC: p95 290ms2026-09-22 UTC: p95 459ms2026-09-23 UTC: p95 291ms2026-09-24 UTC: p95 452ms2026-09-25 UTC: p95 704ms2026-09-26 UTC: p95 502ms2026-09-27 UTC: p95 786ms2026-09-28 UTC: p95 731ms2026-09-29 UTC: p95 722ms2026-09-30 UTC: p95 814ms2026-10-01 UTC: p95 835ms2026-10-02 UTC: p95 555ms2026-10-03 UTC: p95 706ms2026-10-04 UTC: p95 762ms2026-10-05 UTC: p95 529ms
Sep 6Sep 20Oct 5
US-Central
395msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 444ms2026-09-07 UTC: p95 585ms2026-09-08 UTC: p95 577ms2026-09-09 UTC: p95 656ms2026-09-10 UTC: p95 193ms2026-09-11 UTC: p95 219ms2026-09-12 UTC: p95 232ms2026-09-13 UTC: p95 214ms2026-09-14 UTC: p95 177ms2026-09-15 UTC: p95 185ms2026-09-16 UTC: p95 148ms2026-09-17 UTC: p95 130ms2026-09-18 UTC: p95 141ms2026-09-19 UTC: p95 125ms2026-09-20 UTC: p95 116ms2026-09-21 UTC: p95 133ms2026-09-22 UTC: p95 172ms2026-09-23 UTC: p95 270ms2026-09-24 UTC: p95 294ms2026-09-25 UTC: p95 261ms2026-09-26 UTC: p95 490ms2026-09-27 UTC: p95 531ms2026-09-28 UTC: p95 525ms2026-09-29 UTC: p95 598ms2026-09-30 UTC: p95 443ms2026-10-01 UTC: p95 534ms2026-10-02 UTC: p95 501ms2026-10-03 UTC: p95 344ms2026-10-04 UTC: p95 489ms2026-10-05 UTC: p95 395ms
Sep 6Sep 20Oct 5
Canada
95msp95 · 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-06 UTC: p95 448ms2026-09-07 UTC: p95 396ms2026-09-08 UTC: p95 504ms2026-09-09 UTC: p95 436ms2026-09-10 UTC: p95 126ms2026-09-11 UTC: p95 213ms2026-09-12 UTC: p95 252ms2026-09-13 UTC: p95 205ms2026-09-14 UTC: p95 128ms2026-09-15 UTC: p95 213ms2026-09-16 UTC: p95 98ms2026-09-17 UTC: p95 84ms2026-09-18 UTC: p95 76ms2026-09-19 UTC: p95 74ms2026-09-20 UTC: p95 117ms2026-09-21 UTC: p95 131ms2026-09-22 UTC: p95 162ms2026-09-23 UTC: p95 405ms2026-09-24 UTC: p95 408ms2026-09-25 UTC: p95 379ms2026-09-26 UTC: p95 614ms2026-09-27 UTC: p95 616ms2026-09-28 UTC: p95 561ms2026-09-29 UTC: p95 609ms2026-09-30 UTC: p95 628ms2026-10-01 UTC: p95 526ms2026-10-02 UTC: p95 118ms2026-10-03 UTC: p95 174ms2026-10-04 UTC: p95 76ms2026-10-05 UTC: p95 95ms
Sep 6Sep 20Oct 5
UK
410msp95 · 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-06 UTC: p95 405ms2026-09-07 UTC: p95 342ms2026-09-08 UTC: p95 368ms2026-09-09 UTC: p95 352ms2026-09-10 UTC: p95 341ms2026-09-11 UTC: p95 170ms2026-09-12 UTC: p95 169ms2026-09-13 UTC: p95 162ms2026-09-14 UTC: p95 203ms2026-09-15 UTC: p95 195ms2026-09-16 UTC: p95 206ms2026-09-17 UTC: p95 278ms2026-09-18 UTC: p95 235ms2026-09-19 UTC: p95 204ms2026-09-20 UTC: p95 220ms2026-09-21 UTC: p95 249ms2026-09-22 UTC: p95 238ms2026-09-23 UTC: p95 257ms2026-09-24 UTC: p95 280ms2026-09-25 UTC: p95 264ms2026-09-26 UTC: p95 339ms2026-09-27 UTC: p95 325ms2026-09-28 UTC: p95 377ms2026-09-29 UTC: p95 421ms2026-09-30 UTC: p95 328ms2026-10-01 UTC: p95 442ms2026-10-02 UTC: p95 417ms2026-10-03 UTC: p95 415ms2026-10-04 UTC: p95 470ms2026-10-05 UTC: p95 410ms
Sep 6Sep 20Oct 5
Southeast Asia
656msp95 · 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-06 UTC: p95 919ms2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 805ms2026-09-10 UTC: p95 573ms2026-09-11 UTC: p95 857ms2026-09-12 UTC: p95 766ms2026-09-13 UTC: p95 687ms2026-09-14 UTC: p95 571ms2026-09-15 UTC: p95 521ms2026-09-16 UTC: p95 532ms2026-09-17 UTC: p95 741ms2026-09-18 UTC: p95 521ms2026-09-19 UTC: p95 512ms2026-09-20 UTC: p95 453ms2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 732ms2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 972ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 940ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 703ms2026-10-05 UTC: p95 656ms
Sep 6Sep 20Oct 5
Australia
722msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 395ms2026-09-07 UTC: p95 381ms2026-09-08 UTC: p95 373ms2026-09-09 UTC: p95 294ms2026-09-10 UTC: p95 355ms2026-09-11 UTC: p95 529ms2026-09-12 UTC: p95 456ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 542ms2026-09-15 UTC: p95 355ms2026-09-16 UTC: p95 345ms2026-09-17 UTC: p95 359ms2026-09-18 UTC: p95 350ms2026-09-19 UTC: p95 741ms2026-09-20 UTC: p95 701ms2026-09-21 UTC: p95 595ms2026-09-22 UTC: p95 492ms2026-09-23 UTC: p95 561ms2026-09-24 UTC: p95 645ms2026-09-25 UTC: p95 574ms2026-09-26 UTC: p95 698ms2026-09-27 UTC: p95 710ms2026-09-28 UTC: p95 627ms2026-09-29 UTC: p95 717ms2026-09-30 UTC: p95 645ms2026-10-01 UTC: p95 662ms2026-10-02 UTC: p95 700ms2026-10-03 UTC: p95 602ms2026-10-04 UTC: p95 639ms2026-10-05 UTC: p95 722ms
Sep 6Sep 20Oct 5
South America
317msp95 · 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-06 UTC: p95 760ms2026-09-07 UTC: p95 457ms2026-09-08 UTC: p95 545ms2026-09-09 UTC: p95 636ms2026-09-10 UTC: p95 271ms2026-09-11 UTC: p95 311ms2026-09-12 UTC: p95 293ms2026-09-13 UTC: p95 479ms2026-09-14 UTC: p95 442ms2026-09-15 UTC: p95 330ms2026-09-16 UTC: p95 519ms2026-09-17 UTC: p95 631ms2026-09-18 UTC: p95 332ms2026-09-19 UTC: p95 564ms2026-09-20 UTC: p95 355ms2026-09-21 UTC: p95 319ms2026-09-22 UTC: p95 306ms2026-09-23 UTC: p95 318ms2026-09-24 UTC: p95 291ms2026-09-25 UTC: p95 298ms2026-09-26 UTC: p95 302ms2026-09-27 UTC: p95 332ms2026-09-28 UTC: p95 388ms2026-09-29 UTC: p95 483ms2026-09-30 UTC: p95 367ms2026-10-01 UTC: p95 547ms2026-10-02 UTC: p95 306ms2026-10-03 UTC: p95 589ms2026-10-04 UTC: p95 716ms2026-10-05 UTC: p95 317ms
Sep 6Sep 20Oct 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

Get an email when we see WorkOS go down, and when it is back

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.

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: 317msstatus code: 401checked: Oct 5, 2026, 7:53 PM 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: 413msstatus code: 401checked: Oct 5, 2026, 8:07 PM 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: 156msstatus code: 401checked: Oct 5, 2026, 7:27 PM 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: 95msstatus code: 401checked: Oct 5, 2026, 7:29 PM 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: 170msstatus code: 401checked: Oct 5, 2026, 7:17 PM 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: 279msstatus code: 401checked: Oct 5, 2026, 7:47 PM 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: 227msstatus code: 401checked: Oct 5, 2026, 7:21 PM 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: 262msstatus code: 401checked: Oct 5, 2026, 7:58 PM 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: 395msstatus code: 401checked: Oct 5, 2026, 7:32 PM 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: 571msstatus code: 401checked: Oct 5, 2026, 7:54 PM 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

Elevated errors for Audit Logs, 42mdeclared on their status page2026-10-01
Elevated API Errors, 40mdeclared on their status page2026-09-18
Elevated Admin Portal Errors, 52mdeclared on their status page2026-09-14
Form POST failures for some Authkit customers, 2h 2mdeclared on their status page2026-09-09
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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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.