Incidentsby IbisSome customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies
Jul 8, 14:26 UTCJul 8, 21:47 UTC
Duration
7h 21m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-east-1Amazon Web Services (AWS) - us-east-1
Final update
A set of fixes have been implemented and no further latency or failures have been observed in AWS us-east-1 since 17:00 UTC.
Timeline
- Resolved · Jul 8, 21:47 UTC
A set of fixes have been implemented and no further latency or failures have been observed in AWS us-east-1 since 17:00 UTC.
- Monitoring · Jul 8, 19:07 UTC
The service has remained stable since 15:00 UTC. We continue to investigate the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are monitoring for any further occurrences.
- Investigating · Jul 8, 16:46 UTC
We are currently investigating the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are working to mitigate any recurring impact.
- Monitoring · Jul 8, 16:00 UTC
A fix has been implemented and we are monitoring the results.
- Identified · Jul 8, 15:44 UTC
The issue has been identified and a fix is being implemented.
- Monitoring · Jul 8, 15:28 UTC
A fix has been implemented and we are monitoring the results.
- Investigating · Jul 8, 14:26 UTC
Some customers in AWS us-east-1 may experience elevated rate of API errors and 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