Incidentsby IbisElevated latency and errors in GCP us-west1
Oct 14, 13:20 UTCOct 14, 13:36 UTC
Duration
17m
Impact
Informational
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-west1Google Cloud Platform (GCP) - us-west1
Final update
This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.
Timeline
- Resolved · Oct 14, 13:36 UTC
This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.
- Monitoring · Oct 14, 13:20 UTC
Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once monitoring confirms the region is stable.
More from Temporal
Full historyNew namespace creation restricted across all GCP regionsstill openElevated latency and errors in AWS us-east-1lasted 2h 17mElevated error rates for cross-region traffic between US AWS regionslasted 0mElevated GCP storage latency in us-central1 – precautionary namespace failoverlasted 4h 25mIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIlasted 29mUI Disruptions in GCP us-central1lasted 40m