Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients
Delivery to Microsoft-hosted mailboxes has been normal since 12:40 UTC. All delayed emails were delivered. This incident is resolved.
The latest update from Clerk.
State
Resolved
Started
58 d ago
2026-09-04 10:06 UTC
Lasted
4 h 34 min
until 2026-09-04 14:40 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 31 min 33%
Identified
1 h 56 min 42%
Monitoring
1 h 7 min 24%
Updates
Times in UTCAs posted by Clerk
Delivery to Microsoft-hosted mailboxes has been normal since 12:40 UTC. All delayed emails were delivered. This incident is resolved.
Delivery to Microsoft-hosted mailboxes returned to normal at about 12:40 UTC and delayed emails have been delivered. We are monitoring to confirm it stays that way.
We've found the cause. Emails to Microsoft-hosted mailboxes (Outlook.com, Hotmail, Microsoft 365) are being rate limited on the receiving side, and other email senders are seeing the same thing today. Emails are still accepted but some are delayed by several minutes while they're retried. Emails to all other providers are delivering normally. We're monitoring and will update when delivery times return to normal. If a code hasn't arrived, requesting a new one is the fastest workaround.
We are seeing delays in email delivery for recipients on Microsoft-hosted mailboxes (Outlook.com, Hotmail, Microsoft 365). Affected emails, including one-time passcodes and verification links, may arrive late or require re-sending. Emails to other providers are delivering normally. We are working with our email provider to restore normal delivery.
Clerk in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
31
Median duration
3 h 26 min
This incident
1.3× the median
Other Clerk incidents
All incidentsClerk·SMS Delivery Issues
The SMS delivery issue is resolved. Delivery and verification completion rates have returned to normal following our upstream provider’s switch to an alternate route.
Clerk·Issues with Documentation "Ask AI"
The Ask AI functionality in Clerk docs has been restored.
Clerk·Dashboard increased latency
The incident is now resolved
Clerk·Development instances only - Apple rejecting emails
Despite extensive efforts to reach out to Apple about this issue we still do not have a resolution from them. As this incident has been ongoing for over a month, we have decided to move towards displaying a warning message on sign in from development instance when apple emails are used to sign in and taking down this incident notification. We apologize for the inconvenience and genuinely hope that we hear back from Apple soon on this matter.
Clerk·Delays in webhook delivery
All systems are functional
Follow Clerk
Your coding agent knows when Clerk is down, and tells you when a failure is theirs, not yours. You can also get Clerk 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 "clerk" and tell me if Clerk 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=clerk/feed subscribe https://outages.cc/feed.xml?providers=clerkFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane