- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 43of 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 3h 32m it lasted.
Anything that failed between 2026-07-12 22:05 UTC and 2026-07-13 01:37 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
- monitoring
We are observing elevated errors while provisioning domains
provider
- monitoring
The underlying issue has been resolved, a downstream provider incident. Domains which failed to be provisioned are now being reprocessed and succeeding. We are continuing to monitor.
provider
- resolved
All domains have been processed from this incident.
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-880092e451
Is Clerk still down?
No, this incident was resolved 2026-07-13 01:37 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
3h 32m, from 2026-07-12 22:05 UTC to 2026-07-13 01:37 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.