Clerk incident

GCP incident in us-central1-b

Resolved after 3 hours 25 minutes, affecting Authentication & User and Dashboard analytics, on September 1, 2026.

resolved Sep 01, 2026, 07:13 PM 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.

Started
Sep 01, 2026, 03:48 PM UTC
Resolved
Sep 01, 2026, 07:13 PM UTC
Duration
3h 25m
Detected by Pingoru
Sep 01, 2026, 03:48 PM UTC

Affected components

Authentication & UserDashboard analytics

Update timeline

  1. monitoring Sep 01, 2026, 03:48 PM 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. monitoring Sep 01, 2026, 04:13 PM UTC

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

  3. monitoring Sep 01, 2026, 05:30 PM UTC

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

  4. monitoring Sep 01, 2026, 05:49 PM 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. monitoring Sep 01, 2026, 06:35 PM 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. resolved Sep 01, 2026, 07:13 PM 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.

Your product runs on more than Clerk

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →