Clerk reported this minor-impact incident on its official status page on Sep 1, 2026, 15:48 UTC. It was resolved after 3h 26m.
Right now Clerk is degraded. Live Clerk status →
Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.
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.
We are noting recovery in the path between our services and the database provider, but latency and error rate are still elevated above baseline.
The path between our services and the database provider is currently impacted, leading to connection churn and elevated error rates.
Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.
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.
Our 5-minute checks didn't record a change in Clerk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Clerk reported 13 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 2m. See Clerk's uptime and incident history