Incidentsby IbisGCP customers in us-east4 are experiencing elevated errors for Visibility API calls
Jun 8, 22:06 UTCJun 9, 00:59 UTC
Duration
2h 53m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-east4Google Cloud Provider (GCP) - us-east4
Final update
Namespaces have been failed back to their primary region. This incident has been resolved
Timeline
- Resolved · Jun 9, 00:59 UTC
Namespaces have been failed back to their primary region. This incident has been resolved
- Monitoring · Jun 8, 23:18 UTC
The region has recovered , visibility calls are succeeding without errors. We are failing namespaces back in.
- Monitoring · Jun 8, 22:42 UTC
Multi Region Namespaces were failed over at 10:23 PM UTC
- Monitoring · Jun 8, 22:38 UTC
A fix has been implemented and we are monitoring
- Investigating · Jun 8, 22:06 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