Resolved after 3 hours 38 minutes, affecting Authentication & User, on May 8, 2026.
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.
Affected components
Update timeline
- investigating May 08, 2026, 11:02 AM UTC
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 "clerk.[your_domain].com": http://clerk.domain.com, and are working to discover the cause and scope of the issue.
- monitoring May 08, 2026, 11:38 AM UTC
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.
- resolved May 08, 2026, 02:40 PM UTC
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.
Your product runs on more than Clerk
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services