Email delivery delays
WorkOS email delivery to Gmail and Google Workspace addresses is slow, and this affects sign-in codes and the Dashboard and AuthKit components. WorkOS reports that it remediated the issue and now monitors the email delays. The outage started 28 minutes ago and is not resolved.
State
Monitoring
Started
Ongoing for
49 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
28 min 57%
Monitoring
21 min 43%
Updates
Times in UTCAs posted by WorkOS
We've remediated the issue and we're seeing email delays returning to normal levels. We'll continue monitoring.
Some WorkOS emails to Gmail and Google Workspace addresses, including sign-in codes, have been arriving several minutes late. Mail to other providers is not affected. Delayed messages are retried automatically, and we're working to restore normal delivery.
Affected components
4WorkOS in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
17
Median duration
1 h 2 min
This incident
20% shorter than the median
Other WorkOS incidents
All incidentsWorkOS·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.
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.
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