Skip to main content
Vendor reliability

Vendor record

WorkOS

Vendor reports Operational

Checked

Front door check counts and WorkOS’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented WorkOS endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.workos.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every WorkOS product, region or your app worked.

How we count front door checks

WorkOS says

Incident posts from WorkOS’s status page, with its titles, impact levels and times. They say what WorkOS chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

1

incidents WorkOS posted, last 7 days

All vendors’ incidents

Most recent records · all dates

  • Radar SMS challenge failures for phone numbers in mainland China (+86)

    Major

    Started, per WorkOS

    Closed in our record(4h 42m)

    WorkOS’s post

  • Elevated errors for Audit Logs

    Minor

    Started, per WorkOS

    Closed in our record(44m)

    WorkOS’s post

  • Elevated API Errors

    Major

    Started, per WorkOS

    Closed in our record(40m)

    WorkOS’s post

  • Elevated Admin Portal Errors

    Major

    Started, per WorkOS

    Closed in our record(56m)

    WorkOS’s post

  • Static asset delivery failures

    Major

    Started, per WorkOS

    Closed in our record(2h 35m)

    WorkOS’s post
15 older records

  • Degraded outbound email delivery

    Minor

    Started, per WorkOS

    Closed in our record(39m)

    WorkOS’s post

  • Degraded Vault pages in Dashboard

    Not specified

    Started, per WorkOS

    Closed in our record(21m)

    WorkOS’s post

  • Dashboard sign-in errors

    Major

    Started, per WorkOS

    Closed in our record(1h 19m)

    WorkOS’s post

  • Delayed Email Deliverability

    Minor

    Started, per WorkOS

    Closed in our record(1d 21h)

    WorkOS’s post

  • Delayed Email Deliverability

    Not specified

    Started, per WorkOS

    Closed in our record(1h 55m)

    WorkOS’s post

  • Intermittent Dashboard sign-in errors

    Minor

    Started, per WorkOS

    Closed in our record(1h 27m)

    WorkOS’s post

  • Elevated Webhook Errors

    Not specified

    Started, per WorkOS

    Closed in our record(26m)

    WorkOS’s post

  • Elevated Authkit SSO Errors

    Major

    Started, per WorkOS

    Closed in our record(2h 13m)

    WorkOS’s post

  • Delayed Email Deliverability

    Minor

    Started, per WorkOS

    Closed in our record(1h 39m)

    WorkOS’s post

  • Webhook Delivery Delays

    Minor

    Started, per WorkOS

    Closed in our record(2h 11m)

    WorkOS’s post

  • Dashboard email delivery status updates

    Major

    Started, per WorkOS

    Closed in our record(3h 30m)

    WorkOS’s post

  • Elevated errors during email delivery

    Major

    Started, per WorkOS

    Closed in our record(3h 4m)

    WorkOS’s post

  • Email Delivery Delays

    Minor

    Started, per WorkOS

    Closed in our record(1h 24m)

    WorkOS’s post

  • AuthKit SSO failures

    Major

    Started, per WorkOS

    Closed in our record(10m)

    WorkOS’s post

  • Elevated Webhook Latency

    Minor

    Started, per WorkOS

    Closed in our record(52m)

    WorkOS’s post

Your code, your dependencies

See which of your code paths call WorkOS

Connect GitHub or GitLab to find where your public or private repository uses WorkOS. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add WorkOS status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · WorkOSStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/workos?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="WorkOS status badge"></iframe>

Frequently Asked Questions

Is WorkOS currently down?

WorkOS's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did WorkOS last have an outage?

The most recent closed incident record began 1 day ago and spans 4h 42m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for WorkOS?

No. CheckUpstream checks WorkOS’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor WorkOS in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track WorkOS?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors