SMS Delivery Issues

What to do

• Check whether your product depends on Clerk. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 36m it lasted.

  Anything that failed between 2026-10-29 17:40 UTC and 2026-10-29 18:16 UTC may need a replay.

• Subscribe to Clerk's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=clerk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Clerk 6

1. investigatingOct 29, 2026, 5:40 PM UTC

   We’re investigating SMS delivery issues affecting some users. Verification codes may be delayed or fail to arrive.

   provider

2. investigatingOct 29, 2026, 5:46 PM UTC

   We’re investigating SMS delivery issues with an upstream SMS provider.

   provider

3. investigatingOct 29, 2026, 5:54 PM UTC

   We're continuing to investigate SMS delivery issues with an upstream vendor impacting users on AT&T.

   provider

4. investigatingOct 29, 2026, 6:00 PM UTC

   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.

   provider

5. monitoringOct 29, 2026, 6:05 PM UTC

   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.

   provider

6. resolvedOct 29, 2026, 6:16 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.