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-11-05 15:41 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.

Partially degradedchecked 2 minutes ago

WorkOS is answering our probes, but its web surface is running at least 0.4x its 7-day median from Europe and US-West and its sign-in surface is running at least 3.2x its 7-day median from Europe and US-West. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 3:40 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 Nov 5, 2026, 3:40 PM UTC
US-East922 msChecks passing
US-West826 msDegraded
Europe1116 msDegraded
Asia-Pacific1484 msChecks passing
US-Central537 msChecks passing
Canada583 msChecks passing
UK146 msChecks passing
Southeast Asia414 msChecks passing
Australia908 msChecks passing
South America1058 msChecks passing
their status pagetheir claim, not our reading

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

from WorkOS's own status page, checked Nov 5, 2026, 3:13 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

  • AuthKitOperational
  • DashboardOperational
  • Admin PortalOperational
  • SSOOperational
  • Directory SyncOperational
  • Audit LogsOperational
  • 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
1.3sp95 · 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-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 303ms2026-10-23 UTC: p95 199ms2026-10-24 UTC: p95 124ms2026-10-25 UTC: p95 138ms2026-10-26 UTC: p95 491ms2026-10-27 UTC: p95 548ms2026-10-28 UTC: p95 916ms2026-10-29 UTC: p95 750ms2026-10-30 UTC: p95 882ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-West
1.9sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 282ms2026-10-23 UTC: p95 229ms2026-10-24 UTC: p95 214ms2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 361ms2026-10-31 UTC: p95 409ms2026-11-01 UTC: p95 530ms2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · 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-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 522ms2026-10-23 UTC: p95 311ms2026-10-24 UTC: p95 197ms2026-10-25 UTC: p95 216ms2026-10-26 UTC: p95 270ms2026-10-27 UTC: p95 515ms2026-10-28 UTC: p95 441ms2026-10-29 UTC: p95 404ms2026-10-30 UTC: p95 190ms2026-10-31 UTC: p95 190ms2026-11-01 UTC: p95 199ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.2sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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.1s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 417ms2026-10-26 UTC: p95 612ms2026-10-27 UTC: p95 5.6s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
US-Central
1.6sp95 · 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-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 289ms2026-10-23 UTC: p95 265ms2026-10-24 UTC: p95 227ms2026-10-25 UTC: p95 390ms2026-10-26 UTC: p95 473ms2026-10-27 UTC: p95 618ms2026-10-28 UTC: p95 693ms2026-10-29 UTC: p95 757ms2026-10-30 UTC: p95 655ms2026-10-31 UTC: p95 758ms2026-11-01 UTC: p95 747ms2026-11-02 UTC: p95 276ms2026-11-03 UTC: p95 564ms2026-11-04 UTC: p95 522ms2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Canada
1.1sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 322ms2026-10-23 UTC: p95 318ms2026-10-24 UTC: p95 74ms2026-10-25 UTC: p95 218ms2026-10-26 UTC: p95 248ms2026-10-27 UTC: p95 141ms2026-10-28 UTC: p95 157ms2026-10-29 UTC: p95 279ms2026-10-30 UTC: p95 881ms2026-10-31 UTC: p95 886ms2026-11-01 UTC: p95 666ms2026-11-02 UTC: p95 116ms2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
710msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 206ms2026-10-23 UTC: p95 215ms2026-10-24 UTC: p95 187ms2026-10-25 UTC: p95 172ms2026-10-26 UTC: p95 287ms2026-10-27 UTC: p95 232ms2026-10-28 UTC: p95 370ms2026-10-29 UTC: p95 450ms2026-10-30 UTC: p95 452ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 671ms2026-11-02 UTC: p95 250ms2026-11-03 UTC: p95 450ms2026-11-04 UTC: p95 384ms2026-11-05 UTC: p95 710ms
Oct 7Oct 21Nov 5
Southeast Asia
1.9sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 803ms2026-10-23 UTC: p95 581ms2026-10-24 UTC: p95 472ms2026-10-25 UTC: p95 513ms2026-10-26 UTC: p95 785ms2026-10-27 UTC: p95 602ms2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 877ms2026-10-30 UTC: p95 718ms2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 749ms2026-11-03 UTC: p95 977ms2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Australia
1.9sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 394ms2026-10-23 UTC: p95 510ms2026-10-24 UTC: p95 396ms2026-10-25 UTC: p95 694ms2026-10-26 UTC: p95 377ms2026-10-27 UTC: p95 493ms2026-10-28 UTC: p95 596ms2026-10-29 UTC: p95 512ms2026-10-30 UTC: p95 452ms2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
South America
1.5sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 587ms2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 302ms2026-10-25 UTC: p95 357ms2026-10-26 UTC: p95 302ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 456ms2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5

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: Degraded Answering, but 0.4x slower than its 7-day median.Europe: Degraded Answering, but 1.4x slower than its 7-day median.Asia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Degraded Answering, but 3.2x slower than its 7-day median.Europe: Degraded Answering, but 6.4x slower than its 7-day median.Asia-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
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 922msstatus code: 401checked: Nov 5, 2026, 3:20 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
      Degradedlatency: 826msstatus code: 401checked: Nov 5, 2026, 3:20 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: 537msstatus code: 401checked: Nov 5, 2026, 3:22 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: 583msstatus code: 401checked: Nov 5, 2026, 3:21 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: 1058msstatus code: 401checked: Nov 5, 2026, 3:23 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
    DegradedEurope, UK
    • Europe
      Degradedlatency: 1116msstatus code: 401checked: Nov 5, 2026, 3:30 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: 146msstatus code: 401checked: Nov 5, 2026, 3:22 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: 1484msstatus code: 401checked: Nov 5, 2026, 3:08 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: 414msstatus code: 401checked: Nov 5, 2026, 3:35 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: 908msstatus code: 401checked: Nov 5, 2026, 3:40 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

SSO Profile API Timeouts, 2h 18mdeclared on their status page2026-10-29
Elevated errors across SSO and AuthKit, 1h 3mdeclared on their status page2026-10-23
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

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

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>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

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.