# WorkOS: Elevated API Errors

- Provider: [WorkOS](https://outages.cc/workos.md)
- Type: Incident
- State: Resolved
- Worst impact: Partial outage
- Started: 2026-09-18 22:49 UTC
- Resolved: 2026-09-18 23:29 UTC (lasted 40 min)
- Official update: https://stspg.io/9z518xkc2w39

## Updates from WorkOS

### postmortem, 2026-09-22 00:53 UTC

# 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

### resolved, 2026-09-18 23:29 UTC

Our remediations continue to be effective, and services continue to be recovered. We will continue further investigation and additional preventative measures.

### monitoring, 2026-09-18 23:09 UTC

Our initial remediations are in place, and services have recovered. We're continuing to monitor closely.

### identified, 2026-09-18 23:05 UTC

We've identified the root cause, and we're seeing services are beginning to recover. We'll continue to monitor closely and share updates.

### investigating, 2026-09-18 23:01 UTC

We're continuing to investigate this issue to identify the root cause. We'll share another update soon.

### investigating, 2026-09-18 22:49 UTC

We are investigating an issue with our API. We apologize for the inconvenience and will share an update once we have more information.