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.
The latest update from Clerk.
State
Resolved
Started
3 d ago
2026-10-29 17:40 UTC
Lasted
36 min
until 2026-10-29 18:16 UTC
Worst impact
Partial outage
Timeline
6 updatesInvestigating
25 min 68%
Monitoring
12 min 32%
Updates
Times in UTCAs posted by Clerk
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.
SMS verification completion rates have returned to normal levels following the provider’s switch to an alternate delivery route. We’re continuing to monitor delivery and verification rates.
We’ve identified an issue with an upstream SMS provider’s delivery route to AT&T numbers. The provider is switching traffic to an alternate route. We’re monitoring delivery rates and will share updates as we learn more.
We're continuing to investigate SMS delivery issues with an upstream vendor impacting users on AT&T.
We’re investigating SMS delivery issues with an upstream SMS provider.
We’re investigating SMS delivery issues affecting some users. Verification codes may be delayed or fail to arrive.
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
82% shorter than the median
Other Clerk incidents
All incidentsClerk·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
Clerk·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.
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