Incidentsby IbisCustomers in AWS eu-west-1 may experience elevated API latencies
Jul 17, 14:30 UTCJul 17, 15:56 UTC
Duration
1h 26m
Impact
Informational
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
eu-west-1Amazon Web Services (AWS) - eu-west-1
Final update
A spike in workload caused resource contention in the underlying infrastructure, resulting in elevated latency for critical APIs. We scaled up the underlying resources to handle the increased load, and latencies have returned to normal. We will continue to monitor the system, but the mitigation is complete and the incident has been resolved.
Timeline
- Resolved · Jul 17, 15:56 UTC
A spike in workload caused resource contention in the underlying infrastructure, resulting in elevated latency for critical APIs. We scaled up the underlying resources to handle the increased load, and latencies have returned to normal. We will continue to monitor the system, but the mitigation is complete and the incident has been resolved.
- Monitoring · Jul 17, 15:22 UTC
Latencies are back to normal levels, we’re monitoring.
- Investigating · Jul 17, 14:49 UTC
The failover has been completed.
- Investigating · Jul 17, 14:38 UTC
We are failing over MRN namespaces
- Investigating · Jul 17, 14:30 UTC
Customers in AWS eu-west-1 may experience elevated API latencies.
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