- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-central1
- Down Index
- 41of 100
What to do
Check whether you use Clerk in us, us-central1. 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 3h 26m it lasted.
Anything that failed between 2026-09-01 15:48 UTC and 2026-09-01 19:13 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
- monitoring
GCP has several incidents open in us-central1 currently. We are proactively monitoring impact to customer traffic and have so far noted impact to analytics and some of our metrics. We will update shortly with further information.
provider
- monitoring
Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.
provider
- monitoring
The path between our services and the database provider is currently impacted, leading to connection churn and elevated error rates.
provider
- monitoring
We are noting recovery in the path between our services and the database provider, but latency and error rate are still elevated above baseline.
provider
- monitoring
latency metrics have returned to baseline, and we're seeing recovery in error rates. We are continuing to monitor for any signs of resurgence and will update accordingly.
provider
- resolved
Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.
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-a84d69b5d9
Is Clerk still down?
No, this incident was resolved 2026-09-01 19:13 UTC. For Clerk's live state, see https://down.guide/clerk.
How long did it last?
3h 26m, from 2026-09-01 15:48 UTC to 2026-09-01 19:13 UTC, by the times Clerk posted.
What was affected?
Clerk named in us, us-central1.
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.