Incidentsby IbisSome customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.
Jun 12, 19:09 UTCJun 14, 16:06 UTC
Duration
44h 57m
Impact
Informational
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-east-1Amazon Web Services (AWS) - us-east-1
Final update
Incident Resolved.
Timeline
- Resolved · Jun 14, 16:06 UTC
Incident Resolved.
- Monitoring · Jun 12, 23:16 UTC
This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.
- Monitoring · Jun 12, 20:44 UTC
This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.
- Monitoring · Jun 12, 19:09 UTC
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved. We failed namespaces with MRN out of the cell. We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.
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