Is WorkOS down?
Partially downchecked 4 minutes ago
Part of WorkOS is not answering our probes: its web surface from South America. Its sign-in surface, the surface we treat as the service's own, answered from every region we check.
We have an outage open for WorkOS, 1h 48m so far.
Last outage: 57 min on Sep 6, 2026 (web surface, from Australia).
WorkOS reports: All systems operational (“All Systems Operational”)
WorkOS's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)
- 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
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: Down
- AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
Open incident
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 413msstatus code: 401checked: Sep 6, 2026, 6:09 PM UTC0 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-WestOperationallatency: 187msstatus code: 401checked: Sep 6, 2026, 6:10 PM UTC0 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-CentralOperationallatency: 71msstatus code: 401checked: Sep 6, 2026, 6:05 PM UTC0 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.
- CanadaOperationallatency: 286msstatus code: 401checked: Sep 6, 2026, 6:09 PM UTC0 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 AmericaPartially downlatency: 303msstatus code: 401checked: Sep 6, 2026, 5:42 PM UTC0 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.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 606msstatus code: 401checked: Sep 6, 2026, 6:09 PM UTC0 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.
- UKOperationallatency: 317msstatus code: 401checked: Sep 6, 2026, 5:46 PM UTC0 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 PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 446msstatus code: 401checked: Sep 6, 2026, 6:00 PM UTC0 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 AsiaOperationallatency: 589msstatus code: 401checked: Sep 6, 2026, 6:26 PM UTC0 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.
- AustraliaOperationallatency: 283msstatus code: 401checked: Sep 6, 2026, 6:13 PM UTC0 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
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 serversTell me when this goes down
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.
Put this badge in your README
Live, from this page's own readings.[](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 378h 30m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 22 minutes over that period.
By our measurement there is no shortfall to claim for this period.
Separately, we measured 10h 42m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.
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.