- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 27of 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 14m it lasted.
Anything that failed between 2026-07-01 17:12 UTC and 2026-07-01 17:26 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 2
- investigating
We are investigating delays in webhook delivery. We have deployed mitigations and are continuing to monitor.
provider
- resolved
We have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery.
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-df3c6d7a5c
Is Clerk still down?
No, this incident was resolved 2026-07-01 17:26 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
14m, from 2026-07-01 17:12 UTC to 2026-07-01 17:26 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.