Elevated API Errors
# Elevated API Errors **Date:** 09/18/2026 **Duration:** 22:40–23:03 UTC \(23 minutes\) **Status:** Resolved ## Summary On September 18, 2026, from 22:40 to 23:03 UTC, WorkOS experienced an outage affecting authentication and other API requests. Customers encountered failed sign-ins, API errors, timeouts, and long delays. Authentication was most severely affected. An infrastructure failover in the cache supporting our feature-flag system exposed weaknesses in application connection recovery and fallback behavior. Some connections remained stalled after the cache was available again, delaying requests and exhausting database connection pools. Service recovered by 23:03 UTC. We subsequently deployed changes to improve connection recovery. We’re sorry for the disruption this caused you and your users. ## Background WorkOS uses feature flags to control application behavior. The affected backend services read flag data from a shared Redis datastore populated by LaunchDarkly Relay. Each appl
The latest update from WorkOS.
State
Resolved
Started
43 d ago
2026-09-18 22:49 UTC
Lasted
40 min
until 2026-09-18 23:29 UTC
Worst impact
Partial outage
Timeline
6 updatesInvestigating
16 min 41%
Identified
4 min 9%
Monitoring
20 min 50%
Updates
Times in UTCAs posted by WorkOS
# Elevated API Errors **Date:** 09/18/2026 **Duration:** 22:40–23:03 UTC \(23 minutes\) **Status:** Resolved ## Summary On September 18, 2026, from 22:40 to 23:03 UTC, WorkOS experienced an outage affecting authentication and other API requests. Customers encountered failed sign-ins, API errors, timeouts, and long delays. Authentication was most severely affected. An infrastructure failover in the cache supporting our feature-flag system exposed weaknesses in application connection recovery and fallback behavior. Some connections remained stalled after the cache was available again, delaying requests and exhausting database connection pools. Service recovered by 23:03 UTC. We subsequently deployed changes to improve connection recovery. We’re sorry for the disruption this caused you and your users. ## Background WorkOS uses feature flags to control application behavior. The affected backend services read flag data from a shared Redis datastore populated by LaunchDarkly Relay. Each appl
Our remediations continue to be effective, and services continue to be recovered. We will continue further investigation and additional preventative measures.
Our initial remediations are in place, and services have recovered. We're continuing to monitor closely.
We've identified the root cause, and we're seeing services are beginning to recover. We'll continue to monitor closely and share updates.
We're continuing to investigate this issue to identify the root cause. We'll share another update soon.
We are investigating an issue with our API. We apologize for the inconvenience and will share an update once we have more information.
WorkOS in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
17
Median duration
58 min
This incident
31% shorter than the median
Other WorkOS incidents
All incidentsWorkOS·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.
WorkOS·Elevated errors for Audit Logs
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.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