Skip to content

Incident detail

GCP incident in us-central1-b

Resolved incidentMinor

Timeline window

to

Get alerted the next time Clerk breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Clerk posted, oldest to newest, exactly as it appeared on their official status page.

  1. 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.

  2. Monitoring

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

  3. Monitoring

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

  4. 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.

  5. 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.

  6. 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.

Keep exploring

More from Clerk

Neighboring incidents on Clerk's timeline and the rest of their record on OutageDeck.