- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 34of 100
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 5h 55m it lasted.
Anything that failed between 2026-05-22 15:48 UTC and 2026-05-22 21:43 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.
Updates from Clerk 3
- investigating
There is an ongoing issue with one of our upstream providers which is impacting the provisioning of domains.
provider
- monitoring
Our upstream provider has implemented a fix for domain provisioning. We are seeing signs of recovery and are continuing to monitor the situation.
provider
- resolved
Systems are back to normal.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-6852018d37
Is Clerk still down?
No, this incident was resolved 2026-05-22 21:43 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
5h 55m, from 2026-05-22 15:48 UTC to 2026-05-22 21:43 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.