Elevated latency and errors for AuthKit API requests
AuthKit API requests have elevated latency and errors. AuthKit and Core Services - AuthKit are affected in all regions. WorkOS reports that service has recovered fully and WorkOS is monitoring.
State
Monitoring
Started
Ongoing for
59 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
20 min 33%
Monitoring
39 min 67%
Updates
Times in UTCAs posted by WorkOS
From 19:35 to 19:49 UTC AuthKit API request latency and error rates were elevated. Service has since recovered fully and we are monitoring.
We are seeing elevated latency and error rates in AuthKit authentication flows.
Affected components
2WorkOS in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
17
Median duration
1 h 3 min
This incident
About the median
Other WorkOS incidents
All incidentsWorkOS·Intermittent 503 errors in certain regions
WorkOS reported intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. The errors affected the Dashboard, AuthKit, and related services. WorkOS reports that the incident is resolved. It lasted about 4 hours and 19 minutes.
WorkOS·SSO Profile API Timeouts
This incident has been resolved.
WorkOS·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.
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.live/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.live/feed.xml?providers=workos/feed subscribe https://outages.live/feed.xml?providers=workosFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane