# GCP incident in us-central1-b

- Provider: [Clerk](https://down.guide/clerk)
- Level: confirmed
- Impact: Degraded
- lasted 3h 26m
- started 2026-09-01 15:48 UTC
- us, us-central1
- id: DWN-a84d69b5d9
- Official page: https://status.clerk.com/incidents/01M1ETFWW4XQH44X1SZY7RKR8R

## Updates from Clerk
### 2026-09-01 15:48 UTC: 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.

### 2026-09-01 16:13 UTC: monitoring
Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.

### 2026-09-01 17:30 UTC: monitoring
The path between our services and the database provider is currently impacted, leading to connection churn and elevated error rates.

### 2026-09-01 17:49 UTC: 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.

### 2026-09-01 18:35 UTC: 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.

### 2026-09-01 19:13 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).