Incidentsby IbisElevated Errors in us-west-2 Region
Sep 3, 21:12 UTCSep 4, 05:28 UTC
Duration
8h 16m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-west-2Amazon Web Services (AWS) - us-west-2
Final update
As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved.
Timeline
- Resolved · Sep 4, 05:28 UTC
As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved.
- Monitoring · Sep 4, 02:13 UTC
As of 9/4 00:07 UTC, AWS has confirmed the incident impacting us-west-2 is resolved. After a further period of monitoring, we have confirmed service is stable and have begun failing back the affected MRN namespaces.
- Monitoring · Sep 3, 23:25 UTC
We are starting to see recovery as of 23:01 UTC.
- Investigating · Sep 3, 21:12 UTC
We are investigating connectivity errors affecting some customers with namespaces in the us-west-2 region relating to an AWS outage in this region. Our team is actively assessing impact and working on mitigation. Affected MRN namespaces have been failed over. We will provide updates as more information becomes available. https://health.aws.amazon.com/health/status
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