Current answer
Temporal experienced a minor incident: Elevated latency and errors in AWS us-east-1. ServiceAlert observed recovery on Oct 10, 2026.
Looking for an update now? Check the current status, or follow Temporal for future changes.
Incident Lifecycle
Affected Components
us-east-1
Incident Timeline
Monitoring
Latency and error rates in AWS us-east-1 have returned to normal levels and affected namespaces have recovered. We are continuing to monitor the region. We will provide another update once failback is complete.
Oct 9, 2026 at 11:11 PM UTC
Investigating
Mitigation remains in progress. We are continuing to fail over affected namespaces with Multi-Region Replication enabled to their replica regions. Some customers may continue to experience elevated latency while this work is underway. We will provide another update within 30 minutes.
Oct 9, 2026 at 10:50 PM UTC
Investigating
We have identified the cause of elevated latency affecting a subset of namespaces in AWS us-east-1. Namespaces with Multi-Region Replication enabled are being failed over to their replica region to restore service. We will provide another update within 30 minutes.
Oct 9, 2026 at 10:38 PM UTC
Investigating
We are investigating elevated latency and increased deadline exceeded errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.
Oct 9, 2026 at 10:33 PM UTC
Was your business affected by this Temporal outage?
Follow Temporal and route available status alerts to email or a team channel.