outages.live
Live
WorkOSIncident ·

Elevated AuthKit API Error Rates

Partial outageOfficial update
0

AuthKit and Core Services - AuthKit have elevated API error rates. WorkOS reports that the cause is identified and work on a fix continues. The incident started 15 minutes ago and is not resolved.

State

Identified

Started

Ongoing for

37 min

Worst impact

Partial outage

Timeline

2 updates
00:1500:2400:3400:4300:52
Partial outageDegradedUpdate postedTimes in UTC

Investigating

15 min 39%

Identified

23 min 61%

Updates

Times in UTC

As posted by WorkOS

Identified

We are continuing to work on a fix for this issue.

Investigating

We are investigating elevated error rates affecting AuthKit endpoints.

Affected components

2
AuthKitCore Services - AuthKit

WorkOS in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

17

Median duration

1 h 2 min

This incident

39% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 34 min
median 1 h 2 min
90 days agoToday

Other WorkOS incidents

All incidents

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.

Resolved

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.

Resolved

WorkOS·SSO Profile API Timeouts

This incident has been resolved.

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.

Resolved

WorkOS·Elevated AuthKit Error Rates

This incident has been resolved.

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=workos
Slack
/feed subscribe https://outages.live/feed.xml?providers=workos

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane