SSO Profile API Timeouts
This incident has been resolved.
The latest update from WorkOS.
State
Resolved
Started
3 d ago
2026-10-29 17:34 UTC
Lasted
2 h 18 min
until 2026-10-29 19:52 UTC
Worst impact
Partial outage
Timeline
4 updatesInvestigating
20 min 14%
Identified
19 min 14%
Monitoring
1 h 40 min 72%
Updates
Times in UTCAs posted by WorkOS
This incident has been resolved.
We’ve resolved the issue causing timeouts on the SSO profile API and are monitoring.
We've identified the issue causing the SSO profile API timeouts and are working on a fix.
We are investigating timeouts on the /sso/profile endpoint. We apologize for the inconvenience and will share an update once we have more information.
Affected components
2WorkOS in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
17
Median duration
58 min
This incident
2.4× the median
Other WorkOS incidents
All incidentsWorkOS·Elevated errors across SSO and AuthKit
This is now resolved. Errors and latency were elevated between 15:21 and 15:50 UTC primarily for requests served by MIA and ATL with some impact on the US east coast and northern South America.
WorkOS·Elevated AuthKit Error Rates
This incident has been resolved.
WorkOS·Radar SMS challenge failures for phone numbers in mainland China (+86)
We've resolved the issue with Radar SMS challenge verifications to China.
WorkOS·Elevated errors for Audit Logs
This incident has been resolved.
WorkOS·Elevated API and AuthKit errors for some requests (Columbus, OH region)
On October 1, 2026, from 11:34 to 11:40 AM EDT, our CDN provider had a network problem at its Columbus, Ohio location. Some requests to the WorkOS API (api.workos.com) and to AuthKit-hosted pages failed with HTTP 500 or 403 errors. Only requests routed through that location were affected. At the peak, about 8% of all API requests failed, including Audit Logs event ingestion, authentication and Vault decrypt calls. WorkOS systems stayed healthy the whole time and the provider fixed the problem by 11:40 AM EDT. Audit Logs event ingestion (POST /audit_logs/events) was the most affected endpoint: up to 21% of event submissions failed at the peak. Events from failed requests were not recorded. If your application did not retry them, resend any audit log events submitted between 11:34 and 11:40 AM EDT.
Follow WorkOS
Your coding agent knows when WorkOS is down, and tells you when a failure is theirs, not yours. You can also get WorkOS incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "workos" and tell me if WorkOS has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=workos/feed subscribe https://outages.cc/feed.xml?providers=workosFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane