Temporal experienced a major incident on October 20, 2025 affecting us-east-1, lasting 11h 18m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 07:42 AM UTC
Investigating increased latency in control-plane operations for some customers in AWS US-EAST-1 due to ongoing cloud operational issue. Workflow operations are not impacted.
- investigating Oct 20, 2025, 08:07 AM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status Workflow operations are currently not affected.
- identified Oct 20, 2025, 08:11 AM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status There is a loss of OpenMetrics endpoint data for namespaces in us-east-1 Workflow operations are currently not affected.
- monitoring Oct 20, 2025, 10:22 AM UTC
AWS is observing services recovering, see: https://health.aws.amazon.com/health/status Workflow operations are currently not affected.
- monitoring Oct 20, 2025, 03:36 PM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status We are currently seeing network instability in us-east-1. Some customers may see increased latency and error rates in this region.
- monitoring Oct 20, 2025, 04:35 PM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status We are currently seeing network instability in us-east-1. Some customers may see increased latency and error rates in this region.
- monitoring Oct 20, 2025, 04:50 PM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status We are experiencing network instability in us-east-1. Some customers may see increased latency and error rates in this region. We are currently failing over pre-existing multi-region and multi-cloud namespaces to unaffected regions.
- monitoring Oct 20, 2025, 07:34 PM UTC
All pre-existing multi-region and multicloud namespaces to unaffected regions have been failed-over. We are seeing major improvements in networking in the region. We will continue monitoring the situation until full recovery.
- monitoring Oct 20, 2025, 08:40 PM UTC
We continue to see recovery and are actively monitoring stability in the affected region
- resolved Oct 20, 2025, 09:28 PM UTC
Update: Our systems are showing full recovery across all previously impacted namespaces. Namespaces that failed over during the incident have not yet been failed back. We are working directly with a small number of customers on follow-up recovery steps for issues indirectly related to this incident. Update [ 10/22/2025 - 21:00:00Z ] - All multi-region namespaces have been failed back to their preferred region (excluding any namespaces that were specifically requested to not fail back on)