- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 31of 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 1h 16m it lasted.
Anything that failed between 2026-05-28 19:16 UTC and 2026-05-28 20:32 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
We are investigating elevated level of internal errors in APIs.
provider
- monitoring
We have deployed a mitigation to our APIs and observed errors return to a normal level. We are continuing to investigate and monitor.
provider
- resolved
APIs have returned to normal operation.
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-813838369b
Is Clerk still down?
No, this incident was resolved 2026-05-28 20:32 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
1h 16m, from 2026-05-28 19:16 UTC to 2026-05-28 20:32 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.