Incidentsby IbisA small number of customers in AWS us-east-1 experienced elevated latencies.
Mar 17, 01:36 UTCMar 17, 01:36 UTC
Duration
0m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
Not listed by the vendor.
Final update
From approximately 2026-03-17 00:24:00 to 2026-03-17 00:41:00 UTC, a small number of customers in AWS us-east-1 experienced elevated latencies.
Timeline
- Resolved · Mar 17, 01:36 UTC
From approximately 2026-03-17 00:24:00 to 2026-03-17 00:41:00 UTC, a small number of customers in AWS us-east-1 experienced elevated 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