Incidentsby IbisSome customers connecting over PrivateServiceConnect in uscentral1 experienced elevated errors
Apr 9, 00:47 UTCApr 9, 00:47 UTC
Duration
0m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
Not listed by the vendor.
Final update
From 2026-04-09 00:23:00 UTC to 2026-04-09 00:47:15 UTC, some customers using GCP private service connect in us-central1 may have had client connection issues or UNAVAILABLE responses
Timeline
- Resolved · Apr 9, 00:47 UTC
From 2026-04-09 00:23:00 UTC to 2026-04-09 00:47:15 UTC, some customers using GCP private service connect in us-central1 may have had client connection issues or UNAVAILABLE responses
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