Minor impactResolvedAuth

Clerk incident: Sign-in Clerk components unavailable for some domains

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 →

🔔 Get alerted when Clerk has issuesFree · email alerts · no credit card
May 8, 2026, 11:02 UTC
started
May 8, 2026, 14:40 UTC
resolved
3h 38m
duration
Minor
impact
  1. resolvedMay 8, 2026, 14:40 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.

  2. monitoringMay 8, 2026, 11:38 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.

  3. investigatingMay 8, 2026, 11:02 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](http://clerk.domain.com "clerk.[your_domain].com"), and are working to discover the cause and scope of the issue.

What APIStatus.watch saw

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.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Clerk have incidents?

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

Clerk incident on May 8, 2026: Sign-in Clerk components unavailable for some domains · APIStatus.watch