Skip to content

Outage tracker

WorkOS: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, WorkOS's declared record, and how the two compare.

← Back to WorkOS's live status

We started measuring WorkOS on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what WorkOS's own status page declared. Below it, any public chatter we saw about WorkOS and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what WorkOS's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, auth (primary)
Unverified user reportsNo reports about WorkOS in the last 24 hours, which is not evidence that nothing is wrong.
WorkOS's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is WorkOS's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention WorkOS next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%617
US-West100.00%617
Europe99.84%613
Asia-Pacific100.00%598
US-Central100.00%59
Canada100.00%59
UK100.00%58
Southeast Asia100.00%55
Australia100.00%55
South America100.00%57

Monthly summary

Tracking WorkOS since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for WorkOS: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and WorkOS's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for WorkOS in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: WorkOS's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for WorkOS since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

WorkOS's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Static asset delivery failuresPartial outage
Sep 2, 2026, 4:39 PM UTC to Sep 2, 2026, 7:06 PM UTC (2h 27m)resolved
their latest update (Sep 2, 2026, 7:06 PM UTC): Static assets delivery rates have recovered.
Degraded outbound email deliveryMinor incident
Aug 31, 2026, 2:10 PM UTC to Aug 31, 2026, 2:45 PM UTC (35 min)resolved
their latest update (Aug 31, 2026, 2:45 PM UTC): This degradation in delivery was limited to upstream testing infrastructure which has since recovered. There was no external impact.
Degraded Vault pages in DashboardAll systems operational
Aug 27, 2026, 1:48 PM UTC to Aug 27, 2026, 2:04 PM UTC (16 min)resolved
their latest update (Aug 27, 2026, 2:04 PM UTC): The mitigation is in place and errors rates have returned to normal. We will continue to monitor.
Dashboard sign-in errorsPartial outage
Aug 25, 2026, 5:35 PM UTC to Aug 25, 2026, 6:41 PM UTC (1h 5m)resolved
their latest update (Aug 25, 2026, 6:41 PM UTC): This incident is resolved.
Elevated errors on AuthKit authentication endpointsAll systems operational
Aug 19, 2026, 6:14 PM UTC to Aug 19, 2026, 12:00 AM UTC (0 min)resolved
their latest update (Aug 19, 2026, 12:00 AM UTC): On August 18 from 23:59 to 00:03 UTC (August 19), a subset of API requests (primarily AuthKit authentication endpoints) returned HTTP 500 errors. Automatic maintenance of a large, seldom-used internal index caused brief write-ahead-log contention on a primary database that exhaus…
Delayed Email DeliverabilityMinor incident
Aug 15, 2026, 1:35 AM UTC to Aug 16, 2026, 10:04 PM UTC (1d 20h)resolved
their latest update (Aug 16, 2026, 10:04 PM UTC): Microsoft's Outlook team has confirmed that mitigations have been implemented. We've verified that email delivery to Microsoft 365 domains is operating normally again. This incident has been resolved.
Delayed Email DeliverabilityAll systems operational
Aug 14, 2026, 8:14 PM UTC to Aug 14, 2026, 8:45 PM UTC (31 min)resolved
their latest update (Aug 14, 2026, 8:45 PM UTC): This incident has been resolved. Email delivery was delayed between 15:45 EDT and 16:35 EDT due to an issue with an upstream email service provider. This affected customers who have not yet configured a custom email domain or a custom email provider.
Intermittent Dashboard sign-in errorsMinor incident
Aug 11, 2026, 6:02 PM UTC to Aug 11, 2026, 7:24 PM UTC (1h 22m)resolved
their latest update (Aug 11, 2026, 7:24 PM UTC): This incident has been resolved.
Webhook Telemetry IssueAll systems operational
Aug 5, 2026, 6:04 PM UTC to Aug 5, 2026, 6:28 PM UTC (24 min)resolved
their latest update (Aug 5, 2026, 6:28 PM UTC): This was an issue with our internal telemetry - there is no customer impact. Sorry for the false alarm.
Elevated Authkit SSO ErrorsPartial outage
Jul 31, 2026, 4:12 PM UTC to Jul 31, 2026, 6:06 PM UTC (1h 54m)resolved
their latest update (Jul 31, 2026, 6:06 PM UTC): The issue has been resolved.

Showing the 10 most recent of 54 incidents WorkOS has declared in the history we hold.

These entries are WorkOS's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How WorkOS's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording WorkOS's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for WorkOS since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

WorkOS decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If WorkOS believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.