DNS Outage causing critical services to go down

Update timeline

1. investigating Feb 10, 2026, 05:35 PM UTC

   Status: Investigating Our DNS provider is is having an outage, which has caused most of our major services not to resolve. We're currently investigating actively.

2. investigating Feb 10, 2026, 05:50 PM UTC

   Status: Investigating Clerk services are unable to be resolved via DNS due to a provider outage, cached DNS may be keeping things up temporarily Affected components User and authentication (Partial outage) Billing (Partial outage) Machine authentication (Partial outage) Webhooks (Partial outage) B2B SaaS (Partial outage) Email delivery (Full outage) SMS delivery (Full outage)

3. investigating Feb 10, 2026, 05:54 PM UTC

   Status: Investigating In order to mitigate this issue temporarily, we recommend updating your DNS settings as such: CNAME `accounts.` -> `worker.clerkprod-cloudflare.net` CNAME `clerk.` -> `worker.clerkprod-cloudflare.net` Affected components Webhooks (Partial outage) B2B SaaS (Partial outage) Email delivery (Full outage) SMS delivery (Full outage) User and authentication (Partial outage) Billing (Partial outage) Machine authentication (Partial outage)

4. investigating Feb 10, 2026, 06:28 PM UTC

   Status: Investigating For fastest manual recovery, we still recommend updating your own DNS records manually: CNAME `accounts.` -> `worker.clerkprod-cloudflare.net` CNAME `clerk.` -> `worker.clerkprod-cloudflare.net` We also have updated our nameservers to resolve to a fallback DNS provider, though we are observing that propagation is still underway. Once resolution occurs through either approach, most of Clerk's service will recover, but email-based authentication will still encounter validation issues. We are in the process of updating our fallback DNS provider with the appropriate email records. Affected components Machine authentication (Partial outage) Webhooks (Partial outage) B2B SaaS (Partial outage) Email delivery (Full outage) SMS delivery (Full outage) User and authentication (Partial outage) Billing (Partial outage)

5. investigating Feb 10, 2026, 06:45 PM UTC

   Status: Investigating We have restored DNS resolution for `accounts.clerk.services` and `frontend-api.clerk.services` - no need to update DNS records anymore. If you previously updated your DNS records, you can change them back (but if you leave them as they are, it will be fine, nothing will go down). Email/SMS services continue to be impacted by the DNS provider outage. Affected components Billing (Partial outage) Machine authentication (Partial outage) Webhooks (Partial outage) B2B SaaS (Partial outage) Email delivery (Full outage) SMS delivery (Full outage) User and authentication (Partial outage)

6. monitoring Feb 10, 2026, 07:37 PM UTC

   Status: Monitoring We're seeing that most services have recovered, we are still monitoring and will post another update on full recovery. Affected components SMS delivery (Partial outage) User and authentication (Partial outage) Billing (Partial outage) Machine authentication (Partial outage) Webhooks (Partial outage) B2B SaaS (Partial outage) Email delivery (Partial outage)

7. resolved Feb 10, 2026, 07:43 PM UTC

   Status: Resolved Our DNS provider has recovered their services and everything is back online. We are so sorry for the issues and appreciate your patience. A full postmortem will follow, including details on mitigations we will put in place to prevent issues like this in the future. Affected components Email delivery (Operational) SMS delivery (Operational) User and authentication (Operational) Billing (Operational) Machine authentication (Operational) Webhooks (Operational) B2B SaaS (Operational)

8. resolved Feb 13, 2026, 06:17 PM UTC

   Status: Resolved A post-mortem has been published on Clerk's blog. See the write up above for details. Affected components Webhooks (Operational) B2B SaaS (Operational) Email delivery (Operational) SMS delivery (Operational) User and authentication (Operational) Billing (Operational) Machine authentication (Operational)