Clerk: Elevated errors or delays for Clerk application going live

What to do

Check whether your product depends on Clerk. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 41m it lasted.
Anything that failed between 2026-06-12 14:48 UTC and 2026-06-12 15:29 UTC may need a replay.
Subscribe to Clerk's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=clerk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

identifiedJun 12, 2026, 2:48 PM UTC
An upstream provider has a partial outage. Errors or delays might be encountered when a Clerk application goes live. We are monitoring the situation.
provider
monitoringJun 12, 2026, 3:03 PM UTC
A fix has been implemented by the upstream provider. We are monitoring the results
provider
resolvedJun 12, 2026, 3:29 PM UTC
All systems are operational
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Clerk still down?

No, this incident was resolved 2026-06-12 15:29 UTC. For Clerk's live state, see https://down.guide/clerk.

How long did it last?

41m, from 2026-06-12 14:48 UTC to 2026-06-12 15:29 UTC, by the times Clerk posted.

What caused it?

Clerk hasn't published a root cause. If it does, it shows here.

Where does this come from?

Clerk's official status page, https://status.clerk.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.