Is WorkOS down?
For agents
proceed
Proceed.
GET upbutler.com/status/workos/status.agent.json
MCP: upstream_status {"service":"workos"}
SSO, directory sync and AuthKit.
What WorkOS reports
Operational
Taken as is from WorkOS's own status page API. Incident titles and component names below are theirs.
Open status.workos.comUpButler's independent probe
There is no keyless endpoint of WorkOS that says anything useful, so UpButler does not probe it. To check your own WorkOS account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Open at WorkOS
- Scheduled System Maintenancescheduled maintenance
Starts · Dashboard, SSO, Admin Portal, Directory Sync, Audit Logs, AuthKit +1
WorkOS will be undergoing a required platform upgrade on Saturday, October 10th starting at 15:00 UTC and ending at 16:00 UTC. Within this window, we expect a single period of increased latency and error rate lasting up to 2 minutes across all WorkOS products, including event and webhook delivery. Events and webhooks generated during this period may be delayed. If you have any questions, please reach out to [email protected]
Text written by WorkOS, shown unchanged.
WorkOS components
7 operational
Supporting Services
- DashboardOperational
- Admin PortalOperational
Core Services
- SSOOperational
- Directory SyncOperational
- Audit LogsOperational
- AuthKitOperational
- FGAOperational
WorkOS incidents, last 90 days
3 finished incidents seen since UpButler started tracking on 2026-10-10. A typical one lasted under a minute; the longest 42 min.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Elevated errors across SSO and AuthKit sign-in | none | under a minute | |
| Elevated errors for Audit Logs | minor | 42 min | |
| Elevated API and AuthKit errors for some requests (Columbus, OH region) | minor | under a minute |
Tell your outage from WorkOS's
Declare that your project depends on WorkOS. When one of your monitors fails while WorkOS has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- workoscurl -s https://upbutler.com/status/workos/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "workos",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is WorkOS down right now?
- No. As of 2026-10-10 05:08 UTC, WorkOS is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From WorkOS's own status page API at https://status.workos.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are WorkOS's words.
- How can my agent or app check WorkOS status?
- Fetch https://upbutler.com/status/workos/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"workos"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or WorkOS's?
- Add "workos" to the dependencies of your UpButler workspace. When one of your monitors fails while WorkOS has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in authentication
UpButler is not affiliated with WorkOS. Status and incident text belong to WorkOS and are read from their public status source; the probe result is UpButler's own measurement.