Live

Email delivery delays

0

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 updates
18:5919:1119:2419:3619:48
DegradedUpdate postedTimes in UTC

Investigating

28 min 57%

Monitoring

21 min 43%

Updates

Times in UTC

As posted by WorkOS

Monitoring

We've remediated the issue and we're seeing email delays returning to normal levels. We'll continue monitoring.

Investigating

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

4
DashboardAuthKitCore Services - AuthKitSupporting Services - Dashboard

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

20% 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

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