- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 40of 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 41m it lasted.
Anything that failed between 2026-06-09 21:56 UTC and 2026-06-09 22:37 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
Endpoints that use analytics (such as dashboard charts) are encountering timeouts. We are investigating.
provider
- monitoring
We've mitigated a connection issue with the Analytics API and are now monitoring.
provider
- resolved
Between 21:21 and 21:56 UTC on June 9, 2026, a portion of requests to our Analytics service failed and Dashboard charts may have failed to load. The cause was a database connection that had been silently closed upstream but was still being reused by our connection pool. We resolved the issue at 21:56 UTC. No data was lost. To prevent recurrence, we are rolling out a change to detect and self-heal from such failures. We apologize for the disruption
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-594409cab3
Is Clerk still down?
No, this incident was resolved 2026-06-09 22:37 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
41m, from 2026-06-09 21:56 UTC to 2026-06-09 22:37 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.