CheckUpstream measured WorkOS at 100.000% availability across 672 independent checks (global · api). 37 incidents were recorded in the past 12 months; the most recent resolved earlier today after 39 minutes. Status signals are polled from WorkOS's official Atlassian Statuspage status page, alongside independent probes and community reports.
7 days measured availability how this is computed
100.000%
global · api · n=672 · p95 409ms (7d)
Share of our own checks against WorkOS endpoints that returned WorkOS's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 3 incidents · 6 of 7 days with none posted · 1h 7m of declared impact
Fewer incidents in the last 30 days than 9% of 232 tracked services.
Share of each window with no impact declared by WorkOS
7d
99.331%
30d
97.876%
90d
99.284%
180d
99.605%
1y
99.805%
Downtime like this can be refundable
If you're a paying WorkOS customer, outages in these windows may count against WorkOS's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your WorkOS entitlement →Does WorkOS actually matter to you?
A WorkOS outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 31, 14:10 UTC · resolved in 39m · Resolved
Aug 31, 14:10 UTC · resolved in 9m · Resolved
Aug 25, 17:35 UTC · resolved in 1h 19m · Resolved
Live WorkOS status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/workos)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
WorkOS is currently Operational. CheckUpstream tracks WorkOS in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
WorkOS's last resolved incident started earlier today and lasted 39 minutes (degraded performance).
Looking for the live "is WorkOS down" view? See the WorkOS Live status page.
Aug 15, 00:24 UTC · resolved in 1d 21h · Resolved
Aug 15, 00:24 UTC · resolved in 1m · Resolved
Aug 11, 18:02 UTC · resolved in 7m · Resolved
Jul 31, 16:01 UTC · resolved in 13m · Resolved
Jul 29, 18:36 UTC · resolved in 3m · Resolved
Jul 29, 18:30 UTC · resolved in 1h 39m · Resolved
Jul 27, 19:09 UTC · resolved in 2h 11m · Resolved
Jul 27, 14:10 UTC · resolved in 3h 30m · Resolved
Jul 27, 10:05 UTC · resolved in 3h 4m · Resolved
Jul 22, 01:35 UTC · resolved in 1h 24m · Resolved
Jul 21, 21:44 UTC · resolved in 10m · Resolved
Jul 21, 18:58 UTC · resolved in 52m · Resolved
Jul 16, 12:06 UTC · resolved in 23m · Resolved
Jul 16, 08:26 UTC · resolved in 2h 23m · Resolved
Jun 24, 16:44 UTC · resolved in 12h 35m · Resolved
WorkOS's 30-day measured availability is 100.000%, from CheckUpstream's own probes against WorkOS endpoints. It is the share of checks that returned the expected response, not a figure taken from WorkOS's status page.
Sign up to CheckUpstream and add WorkOS to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll WorkOS's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.