Changes / WorkOS / SSO API Latency Degradation Caused by Transient Capacity Constraints
WorkOS: Major incident: SSO API Latency Degradation Caused by Transient Capacity Constraints
Summary
WorkOS reported major SSO degradation, with increased latency and intermittent timeouts between 14:40 and 14:53 UTC, caused by temporarily reduced capacity following an infrastructure event. The incident record started at 2026-04-20 19:16 UTC and resolved at 2026-04-20 19:17 UTC (1 min); SSO login performance returned to normal.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 97%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: SSO API Latency Degradation Caused by Transient Capacity Constraints
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-20 19:16 UTC
Before: not present
After: 2026-04-20 19:17 UTC
Before: not present
After: AuthKit, Core Services - AuthKit, Core Services - SSO, SSO
Before: not present
After: Between 14:40 and 14:53 UTC, SSO endpoints experienced increased latency and intermittent timeouts. The issue was caused by a temporary reduction in available capacity due to an underlying infrastructure event, which led to a brief period of degraded performance
Before: not present
After: The issue has been resolved, and SSO login performance has returned to normal. We will continue to monitor closely to ensure stability.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: SSO API Latency Degradation Caused by Transient Capacity Constraints (this change) WorkOS reported major SSO degradation, with increased latency and intermittent timeouts between 14:40 and 14:53 UTC, caused by temporarily reduced capacity following an infrastructure event. The incident record started at 2026-04-20 19:16 UTC and resolved at 2026-04-20 19:17 UTC (1 min); SSO login performance returned to normal. | Major incident |