- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 2m it lasted.
Anything that failed between 2026-07-16 07:56 UTC and 2026-07-16 07:58 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
There is increased latency on our APIs. We are investigating.
provider
- resolved
There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels.
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-a6895e8d8d
Is Clerk still down?
No, this incident was resolved 2026-07-16 07:58 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
2m, from 2026-07-16 07:56 UTC to 2026-07-16 07:58 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.