Customers in us-west-2 may experience unavailability of service
Nov 18, 06:15 UTCNov 18, 06:15 UTC
Duration
0m
Impact
Informational
Root cause
Network
Temporal, 90 days
27 incidents
Affected
Not listed by the vendor.
Final update
Customers in us-west-2 may have experienced service unavailability for approximately 8 minutes between 06:10:15 UTC to 06:18:00 UTC. We’ve identified and resolved the issue caused by a spike in activity affecting one of our networking services. The source has been isolated and will not recur. As a precaution, we’re doubling capacity in the affected region and will complete a full analysis to further strengthen our protections.
Timeline
- Resolved · Nov 18, 06:15 UTC
Customers in us-west-2 may have experienced service unavailability for approximately 8 minutes between 06:10:15 UTC to 06:18:00 UTC. We’ve identified and resolved the issue caused by a spike in activity affecting one of our networking services. The source has been isolated and will not recur. As a precaution, we’re doubling capacity in the affected region and will complete a full analysis to further strengthen our protections.
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