GCP incident in us-central1-b

Zeitverlauf

1. 15:48 UTC Statusseite von Clerk · Reported GCP incident in us-central1-b
2. 15:48 UTC Statusseite von Clerk · Wird beobachtet 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.
3. 16:13 UTC Statusseite von Clerk · Wird beobachtet Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.
4. 17:30 UTC Statusseite von Clerk · Wird beobachtet The path between our services and the database provider is currently impacted, leading to connection churn and elevated error rates.
5. 17:49 UTC Statusseite von Clerk · Wird beobachtet We are noting recovery in the path between our services and the database provider, but latency and error rate are still elevated above baseline.
6. 18:35 UTC Statusseite von Clerk · Wird beobachtet 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.
7. 19:13 UTC Statusseite von Clerk · Behoben Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.