- 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 8m it lasted.
Anything that failed between 2026-09-16 12:31 UTC and 2026-09-16 13:39 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 6
- identified
Currently there are delays for some customers in webhook delivery. The issue has been identified and we are working towards a resolution
provider
- monitoring
A mitigation has been applied. Webhooks are being delivered at the normal pace. We continue monitoring
provider
- resolved
All systems are working
provider
- investigating
Delays in webhook deliveries for some customers
provider
- monitoring
Webhook delivery is normal at the moment. We are closely monitoring
provider
- resolved
All systems are functional
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-e06fdfd13a
Is Clerk still down?
No, this incident was resolved 2026-09-16 13:39 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
1h 8m, from 2026-09-16 12:31 UTC to 2026-09-16 13:39 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.