Elevated AuthKit errors
For about 62 seconds, from 2026-11-22 05:31:27 to 2026-11-22 05:32:28 UTC, we experienced elevated error rates for AuthKit API requests. Error rates have since returned to normal.
The latest update from WorkOS.
State
Resolved
Started
Lasted
1 min
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by WorkOS
For about 62 seconds, from 2026-11-22 05:31:27 to 2026-11-22 05:32:28 UTC, we experienced elevated error rates for AuthKit API requests. Error rates have since returned to normal.
Affected components
2WorkOS in the last 90 days
Full historyIncidents in 90 days
18
Days with an incident
18
Median duration
1 h 2 min
This incident
100% shorter than the median
Other WorkOS incidents
All incidentsWorkOS·Email delivery delays
WorkOS email delivery was delayed for Gmail and Google Workspace addresses, including sign-in codes. The Dashboard and AuthKit components were affected. WorkOS reports that the incident is resolved and lasted 2 hours and 22 minutes.
WorkOS·Elevated AuthKit API Error Rates
AuthKit endpoints have high error rates. The AuthKit and Core Services - AuthKit components are affected. WorkOS reports that the incident is resolved. It lasted 68 minutes.
WorkOS·Elevated latency and errors for AuthKit API requests
AuthKit API requests had elevated latency and errors. The incident affected AuthKit and Core Services - AuthKit. WorkOS reports that the incident is resolved and lasted 60 minutes.
WorkOS·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.
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