Clerk vs WorkOS
Independent checks, recorded incidents and SLA terms for these vendors.
30-day window ending
Independent checks
Probes check endpoint responses. A passing check does not confirm that a customer action worked.
| Last 30 days | Clerk | WorkOS |
|---|---|---|
| Passing checks | 100.000% 2,880 conclusive checks | 100.000% 2,880 conclusive checks |
| Response time95th percentile | 311 ms | 396 ms |
Response time uses successful checks only: 95% returned within this duration. Different endpoints and regions can produce different results.
Clerk · check scope
apiRegion not recorded
api.clerk.com
- First sample in this window
- Latest recorded sample
WorkOS · check scope
apiRegion not recorded
api.workos.com
- First sample in this window
- Latest recorded sample
What the incident records say
Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.
| Last 30 days | Clerk | WorkOS |
|---|---|---|
| Incidents recorded | 5 | 6 |
| Recorded incident durationMedian | 1h 9m 5 valid durations | 41m 6 valid durations |
Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not mean an outage is ongoing.
Clerk
Delays in webhook delivery
- Started
- Closed in record
Maintenance: Scheduled database maintenance — brief write interruption
- Started
- Closed in record
Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients
- Started
- Closed in record
WorkOS
Elevated API Errors
- Started
- Closed in record
Elevated Admin Portal Errors
- Started
- Closed in record
Static asset delivery failures
- Started
- Closed in record
Check the terms for your plan
An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.