Clerk reported this minor-impact incident on its official status page on May 8, 2026, 11:02 UTC. It was resolved after 3h 38m.
Right now Clerk is degraded. Live Clerk status →
We continue to work with our DNS provider to discover the source of the issue. We currently believe approximately 0.37% of traffic was impacted by being unable to resolve DNS of the CDN that provides ClerkJS.
We have observed that failures to load Clerk JS (reported by [dashboard.clerk.com](http://dashboard.clerk.com)) last occurred 30minutes ago, and this would correlate with failures reported from Clerk applications. We are in contact with our DNS providers to understand the root cause.
We are currently investigating an issue where Clerk JS cannot be downloaded, preventing sign in or sign up when using Clerk components. We believe this is related to DNS [clerk.[your_domain].com](http://clerk.domain.com "clerk.[your_domain].com"), and are working to discover the cause and scope of the issue.
Our 5-minute checks didn't record a change in Clerk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Clerk reported 13 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 2m. See Clerk's uptime and incident history