Incidentsby IbisSome customers in GCP us-east4 may experience elevated latencies
Jul 20, 17:44 UTCJul 20, 19:55 UTC
Duration
2h 11m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-east4Google Cloud Provider (GCP) - us-east4
Final update
This incident has been resolved.
Timeline
- Resolved · Jul 20, 19:55 UTC
This incident has been resolved.
- Monitoring · Jul 20, 19:33 UTC
The affected infrastructure has recovered. Latencies and error rates have returned to normal, and workloads have resumed.
- Monitoring · Jul 20, 19:04 UTC
A fix has been implemented and we are monitoring the results.
- Identified · Jul 20, 19:03 UTC
A fix has been implemented and we are continuing to monitor.
- Identified · Jul 20, 18:57 UTC
We have mitigated the primary impact, and service has been restored for most affected customers. Recovery efforts continue for the remaining infrastructure, with a small number of customer namespaces still affected. Our engineering team is actively working to complete restoration and will provide another update as progress is made.
- Investigating · Jul 20, 17:44 UTC
We are currently investigating this issue
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