Skip to content

Outage tracker / WorkOS

Is WorkOS down?

I'm having a problem

Vendor reports no incidentWhat WorkOS reports

WorkOS reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:48 UTC.

WorkOS's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 8 minutes ago

Our checks of WorkOS pass from all 10 regions we check.

As of Oct 22, 2026, 9:44 PM UTC, RealUptime's checks of WorkOS passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:44 PM UTC
US-East44 msChecks passing
US-West151 msChecks passing
Europe134 msChecks passing
Asia-Pacific909 msChecks passing
US-Central72 msChecks passing
Canada60 msChecks passing
UK121 msChecks passing
Southeast Asia361 msChecks passing
Australia388 msChecks passing
South America337 msChecks passing
their status pagetheir claim, not our reading

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

from WorkOS's own status page, checked Oct 22, 2026, 9:33 PM UTC
WorkOS's own status page shows no incident, and our checks of WorkOS pass 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
307msp95 · 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-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 292ms2026-10-06 UTC: p95 413ms2026-10-07 UTC: p95 386ms2026-10-08 UTC: p95 515ms2026-10-09 UTC: p95 396ms2026-10-10 UTC: p95 393ms2026-10-11 UTC: p95 425ms2026-10-12 UTC: p95 417ms2026-10-13 UTC: p95 495ms2026-10-14 UTC: p95 413ms2026-10-15 UTC: p95 364ms2026-10-16 UTC: p95 161ms2026-10-17 UTC: p95 117ms2026-10-18 UTC: p95 127ms2026-10-19 UTC: p95 197ms2026-10-20 UTC: p95 322ms2026-10-21 UTC: p95 594ms2026-10-22 UTC: p95 307ms
Sep 23Oct 7Oct 22
US-West
282msp95 · 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-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 473ms2026-10-06 UTC: p95 426ms2026-10-07 UTC: p95 436ms2026-10-08 UTC: p95 462ms2026-10-09 UTC: p95 414ms2026-10-10 UTC: p95 417ms2026-10-11 UTC: p95 400ms2026-10-12 UTC: p95 417ms2026-10-13 UTC: p95 592ms2026-10-14 UTC: p95 529ms2026-10-15 UTC: p95 528ms2026-10-16 UTC: p95 314ms2026-10-17 UTC: p95 298ms2026-10-18 UTC: p95 210ms2026-10-19 UTC: p95 232ms2026-10-20 UTC: p95 213ms2026-10-21 UTC: p95 283ms2026-10-22 UTC: p95 282ms
Sep 23Oct 7Oct 22
Europe
526msp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 386ms2026-10-06 UTC: p95 405ms2026-10-07 UTC: p95 3.1s2026-10-08 UTC: p95 569ms2026-10-09 UTC: p95 435ms2026-10-10 UTC: p95 442ms2026-10-11 UTC: p95 510ms2026-10-12 UTC: p95 337ms2026-10-13 UTC: p95 278ms2026-10-14 UTC: p95 310ms2026-10-15 UTC: p95 575ms2026-10-16 UTC: p95 581ms2026-10-17 UTC: p95 820ms2026-10-18 UTC: p95 962ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 290ms2026-10-21 UTC: p95 259ms2026-10-22 UTC: p95 526ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 606ms2026-10-06 UTC: p95 493ms2026-10-07 UTC: p95 688ms2026-10-08 UTC: p95 756ms2026-10-09 UTC: p95 682ms2026-10-10 UTC: p95 675ms2026-10-11 UTC: p95 898ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1s2026-10-14 UTC: p95 922ms2026-10-15 UTC: p95 890ms2026-10-16 UTC: p95 622ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 440ms2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
US-Central
292msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 388ms2026-10-06 UTC: p95 425ms2026-10-07 UTC: p95 338ms2026-10-08 UTC: p95 400ms2026-10-09 UTC: p95 511ms2026-10-10 UTC: p95 457ms2026-10-11 UTC: p95 403ms2026-10-12 UTC: p95 310ms2026-10-13 UTC: p95 315ms2026-10-14 UTC: p95 315ms2026-10-15 UTC: p95 198ms2026-10-16 UTC: p95 464ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 249ms2026-10-21 UTC: p95 132ms2026-10-22 UTC: p95 292ms
Sep 23Oct 7Oct 22
Canada
348msp95 · 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-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 100ms2026-10-06 UTC: p95 217ms2026-10-07 UTC: p95 199ms2026-10-08 UTC: p95 147ms2026-10-09 UTC: p95 307ms2026-10-10 UTC: p95 278ms2026-10-11 UTC: p95 337ms2026-10-12 UTC: p95 282ms2026-10-13 UTC: p95 328ms2026-10-14 UTC: p95 301ms2026-10-15 UTC: p95 273ms2026-10-16 UTC: p95 106ms2026-10-17 UTC: p95 86ms2026-10-18 UTC: p95 95ms2026-10-19 UTC: p95 176ms2026-10-20 UTC: p95 200ms2026-10-21 UTC: p95 553ms2026-10-22 UTC: p95 348ms
Sep 23Oct 7Oct 22
UK
206msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 417ms2026-10-06 UTC: p95 417ms2026-10-07 UTC: p95 399ms2026-10-08 UTC: p95 409ms2026-10-09 UTC: p95 448ms2026-10-10 UTC: p95 407ms2026-10-11 UTC: p95 425ms2026-10-12 UTC: p95 416ms2026-10-13 UTC: p95 311ms2026-10-14 UTC: p95 323ms2026-10-15 UTC: p95 313ms2026-10-16 UTC: p95 317ms2026-10-17 UTC: p95 553ms2026-10-18 UTC: p95 638ms2026-10-19 UTC: p95 796ms2026-10-20 UTC: p95 231ms2026-10-21 UTC: p95 219ms2026-10-22 UTC: p95 206ms
Sep 23Oct 7Oct 22
Southeast Asia
827msp95 · 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-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 645ms2026-10-06 UTC: p95 595ms2026-10-07 UTC: p95 782ms2026-10-08 UTC: p95 797ms2026-10-09 UTC: p95 791ms2026-10-10 UTC: p95 772ms2026-10-11 UTC: p95 783ms2026-10-12 UTC: p95 753ms2026-10-13 UTC: p95 857ms2026-10-14 UTC: p95 888ms2026-10-15 UTC: p95 811ms2026-10-16 UTC: p95 513ms2026-10-17 UTC: p95 788ms2026-10-18 UTC: p95 438ms2026-10-19 UTC: p95 453ms2026-10-20 UTC: p95 492ms2026-10-21 UTC: p95 543ms2026-10-22 UTC: p95 827ms
Sep 23Oct 7Oct 22
Australia
395msp95 · 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-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 713ms2026-10-06 UTC: p95 550ms2026-10-07 UTC: p95 500ms2026-10-08 UTC: p95 456ms2026-10-09 UTC: p95 517ms2026-10-10 UTC: p95 539ms2026-10-11 UTC: p95 585ms2026-10-12 UTC: p95 561ms2026-10-13 UTC: p95 730ms2026-10-14 UTC: p95 539ms2026-10-15 UTC: p95 448ms2026-10-16 UTC: p95 515ms2026-10-17 UTC: p95 556ms2026-10-18 UTC: p95 526ms2026-10-19 UTC: p95 663ms2026-10-20 UTC: p95 478ms2026-10-21 UTC: p95 429ms2026-10-22 UTC: p95 395ms
Sep 23Oct 7Oct 22
South America
594msp95 · 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-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 349ms2026-10-06 UTC: p95 310ms2026-10-07 UTC: p95 500ms2026-10-08 UTC: p95 360ms2026-10-09 UTC: p95 323ms2026-10-10 UTC: p95 447ms2026-10-11 UTC: p95 449ms2026-10-12 UTC: p95 323ms2026-10-13 UTC: p95 401ms2026-10-14 UTC: p95 345ms2026-10-15 UTC: p95 283ms2026-10-16 UTC: p95 329ms2026-10-17 UTC: p95 544ms2026-10-18 UTC: p95 396ms2026-10-19 UTC: p95 316ms2026-10-20 UTC: p95 693ms2026-10-21 UTC: p95 416ms2026-10-22 UTC: p95 594ms
Sep 23Oct 7Oct 22

Check your own site while you wait on WorkOS

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when WorkOS reports an incident on its status page, and again when it reports it resolved.

Get an email when WorkOS reports an incident

Email me when WorkOS reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is WorkOS's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 44msstatus code: 401checked: Oct 22, 2026, 9:44 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
      Checks passinglatency: 151msstatus code: 401checked: Oct 22, 2026, 9:34 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
      Checks passinglatency: 72msstatus code: 401checked: Oct 22, 2026, 9:32 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
      Checks passinglatency: 60msstatus code: 401checked: Oct 22, 2026, 9:31 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
    Checks passinglatency: 337msstatus code: 401checked: Oct 22, 2026, 9:33 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 134msstatus code: 401checked: Oct 22, 2026, 9:33 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
      Checks passinglatency: 121msstatus code: 401checked: Oct 22, 2026, 9:33 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 909msstatus code: 401checked: Oct 22, 2026, 9:37 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
      Checks passinglatency: 361msstatus code: 401checked: Oct 22, 2026, 9:33 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
      Checks passinglatency: 388msstatus code: 401checked: Oct 22, 2026, 9:32 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 probe events

Elevated AuthKit Error Rates, 58mdeclared on their status page2026-10-19
Radar SMS challenge failures for phone numbers in mainland China (+86), 4h 34mdeclared on their status page2026-10-15
Elevated errors across SSO and AuthKit sign-in, 1mdeclared on their status page2026-10-09
Elevated errors for Audit Logs, 42mdeclared on their status page2026-10-01
Elevated API and AuthKit errors for some requests (Columbus, OH region), 1mdeclared 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

check 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 check readings and WorkOS's own claim at the time, side by side.

Full check history for WorkOS: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![WorkOS uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is WorkOS down?", https://realuptime.io/outages/workos. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.workos.com

RealUptime is not affiliated with WorkOS; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.