# Clerk: GCP incident in us-central1-b

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-09-01 15:48 UTC · Resolved: 2026-09-01 19:13 UTC · Duration: 3.4 h
- Updates: 6 · Affected components: Dashboard analytics, Authentication & User
- [Vendor status page: https://status.clerk.com/incidents/01M1ETFWW4XQH44X1SZY7RKR8R](https://status.clerk.com/incidents/01M1ETFWW4XQH44X1SZY7RKR8R)
- [Company: Clerk](https://rewindex.com/company/clerk.md)

## Timeline of updates

- **monitoring** 2026-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.
- **monitoring** 2026-09-01 16:13 UTC: Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.
- **monitoring** 2026-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.
- **monitoring** 2026-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.
- **monitoring** 2026-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.
- **resolved** 2026-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.


---
Canonical: https://rewindex.com/company/clerk/incidents/01M1ETFWW4XQH44X1SZY7RKR8R · Markdown: https://rewindex.com/company/clerk/incidents/01M1ETFWW4XQH44X1SZY7RKR8R.md · JSON: https://rewindex.com/api/v1/companies/clerk/incidents/01M1ETFWW4XQH44X1SZY7RKR8R · Generated 2026-10-18T10:43:18.179Z