- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 36of 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 14h 19m it lasted.
Anything that failed between 2026-10-01 16:10 UTC and 2026-10-02 06: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.
Updates from Clerk 4
- investigating
We are investigating increased latency for the Clerk Dashboard!
provider
- identified
Latency is back to normal. We have identified the issue and are actively working on fixing it.
provider
- monitoring
We have implemented a fix for this incident and are monitoring to ensure the issue does not recur.
provider
- resolved
The incident is now resolved
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-26867e447c
Is Clerk still down?
No, this incident was resolved 2026-10-02 06:29 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
14h 19m, from 2026-10-01 16:10 UTC to 2026-10-02 06: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.