← Back to Clerk History
minor✓ Resolved
GCP incident in us-central1-b
Status
resolved
Duration
3h 26m
Updates
6
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
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.
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.
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.
monitoring
The path between our services and the database provider is currently impacted, leading to connection churn and elevated error rates.
monitoring
Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.
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.
📊 TECHNICAL DETAILS
Internal ID
45f1bab1-2539-47d4-955b-66b3a8989117
External ID
01M1ETFWW4XQH44X1SZY7RKR8R
🕐 First reported
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
3h 26m
Total Duration
6
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed