Companies / Clerk / incidents

Clerk: GCP incident in us-central1-b

Affected components: Dashboard analyticsAuthentication & User

Timeline of updates

1. monitoring2026-09-01 15:48 UTC

   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.

2. monitoring2026-09-01 16:13 UTC

   Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.

3. monitoring2026-09-01 17:30 UTC

   The path between our services and the database provider is currently impacted, leading to connection churn and elevated error rates.

4. monitoring2026-09-01 17:49 UTC

   We are noting recovery in the path between our services and the database provider, but latency and error rate are still elevated above baseline.

5. monitoring2026-09-01 18:35 UTC

   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.

6. resolved2026-09-01 19:13 UTC

   Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.

Impact, status and times are the vendor’s own, as last archived. View on status.clerk.com (opens in new tab). Clerk profile · Recent Clerk incidents · Markdown · JSON