Vendor record
WorkOS
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 checksWorkOS 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.
35
incidents WorkOS posted, last 180 days
Median recorded duration: 1h 19m. From 35 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Radar SMS challenge failures for phone numbers in mainland China (+86)
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(4h 42m)
Elevated errors for Audit Logs
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(44m)
Elevated API Errors
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(40m)
Elevated Admin Portal Errors
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(56m)
Static asset delivery failures
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(2h 35m)
15 older records
Degraded outbound email delivery
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(39m)
Degraded Vault pages in Dashboard
Not specifiedWorkOS’s postStarted, per WorkOS
Closed in our record(21m)
Dashboard sign-in errors
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(1h 19m)
Delayed Email Deliverability
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(1d 21h)
Delayed Email Deliverability
Not specifiedWorkOS’s postStarted, per WorkOS
Closed in our record(1h 55m)
Intermittent Dashboard sign-in errors
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(1h 27m)
Elevated Webhook Errors
Not specifiedWorkOS’s postStarted, per WorkOS
Closed in our record(26m)
Elevated Authkit SSO Errors
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(2h 13m)
Delayed Email Deliverability
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(1h 39m)
Webhook Delivery Delays
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(2h 11m)
Dashboard email delivery status updates
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(3h 30m)
Elevated errors during email delivery
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(3h 4m)
Email Delivery Delays
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(1h 24m)
AuthKit SSO failures
MajorWorkOS’s postStarted, per WorkOS
Closed in our record(10m)
Elevated Webhook Latency
MinorWorkOS’s postStarted, per WorkOS
Closed in our record(52m)
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.
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.
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.