Incidentsby IbisElevated error rates in GCP us-central1
Sep 1, 15:47 UTCSep 1, 21:43 UTC
Duration
5h 56m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-central1Google Cloud Provider (GCP) - us-central1
Final update
GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.
Timeline
- Resolved · Sep 1, 21:43 UTC
GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.
- Identified · Sep 1, 16:07 UTC
We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
- Investigating · Sep 1, 15:47 UTC
We are currently investigating elevated error rates in GCP us-central1, and have failed over MRN namespaces in this region.
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 0mElevated GCP storage latency in us-central1 – precautionary namespace failoverlasted 4h 25mIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIlasted 29m