We're seeing that most services have recovered, we are still monitoring and will post another update on full recovery.
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.
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.
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`
Clerk services are unable to be resolved via DNS due to a provider outage, cached DNS may be keeping things up temporarily
Our DNS provider is is having an outage, which has caused most of our major services not to resolve. We're currently investigating actively.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 5850 services available
Integrations with