Incidentsby IbisElevated GCP storage latency in us-central1 – precautionary namespace failover
Oct 8, 21:53 UTCOct 9, 02:17 UTC
Duration
4h 25m
Impact
Informational
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
Not listed by the vendor.
Final update
This incident is now resolved.
Timeline
- Resolved · Oct 9, 02:17 UTC
This incident is now resolved.
- Monitoring · Oct 9, 01:04 UTC
Cloud Storage latency in GCP us-central1 has returned to normal levels. We are continuing to monitor the region and will begin failing multi-region namespaces back to us-central1 shortly.
- Investigating · Oct 8, 21:53 UTC
We are monitoring elevated Cloud Storage latency from GCP in us-central1. As a precaution, multi-region namespaces in this region have been failed over to their replica regions. No impact to workflow execution has been observed. We will fail back once GCP confirms recovery.
More from Temporal
Full historyNew namespace creation restricted across all GCP regionsstill openElevated latency and errors in GCP us-west1lasted 17mElevated latency and errors in AWS us-east-1lasted 2h 17mElevated error rates for cross-region traffic between US AWS regionslasted 0mIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIlasted 29mUI Disruptions in GCP us-central1lasted 40m