A GCP incident in us-central1 caused disruptions to Clerk's analytics, internal metrics, and database connectivity over approximately 3.5 hours. The connectivity issues between Clerk's services and its database provider resulted in connection churn and elevated error rates. Recovery was observed progressively, with latency and error rates returning to baseline by the end of the incident.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with