Clerk incident

Sign-in Clerk components unavailable for some domains

Minor Resolved View vendor source →

Clerk experienced a minor incident on May 8, 2026 affecting User and authentication, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 08, 2026, 02:40 PM UTC
Resolved
May 08, 2026, 02:40 PM UTC
Duration
Detected by Pingoru
May 08, 2026, 02:40 PM UTC

Affected components

User and authentication

Update timeline

  1. investigating May 08, 2026, 11:02 AM UTC

    Status: Investigating 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. Affected components User and authentication (Partial outage)

  2. monitoring May 08, 2026, 11:38 AM UTC

    Status: Monitoring 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. Affected components User and authentication (Degraded performance)

  3. resolved May 08, 2026, 02:40 PM UTC

    Status: Resolved 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 User and authentication (Operational)