Temporal incident
Some customers in AWS us-east-1 may experience elevated API latencies
Temporal experienced a minor incident on May 8, 2026 affecting us-east-1, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 01:14 AM UTC
Some customers in AWS us-east-1 may experience elevated API latencies.
- identified May 08, 2026, 01:50 AM UTC
We are proactively failing all AWS us-east-1 multi‑region replication enabled primary namespaces due to ongoing AWS incident https://health.aws.amazon.com/health/status?path=open-issues
- identified May 08, 2026, 02:55 AM UTC
We are continuing to work closely with AWS as they address the underlying issue. We are also actively monitoring the health of impacted namespaces.
- identified May 08, 2026, 03:40 AM UTC
We are continuing to work closely with AWS as they address the underlying issue and are actively monitoring impacted multi-region replication-enabled namespaces for stability. We have also confirmed those namespaces are in their expected replication configuration.
- identified May 08, 2026, 07:43 AM UTC
We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.
- monitoring May 08, 2026, 09:27 AM UTC
We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable.
- monitoring May 08, 2026, 12:29 PM UTC
We continue to monitor the situation and the service stability has been maintained.
- monitoring May 08, 2026, 05:37 PM UTC
AWS continues to work to resolve the underlying infrastructure issues in us-east-1. We continue to monitor our service closely, and we have not observed any new impact.
- resolved May 09, 2026, 03:56 AM UTC
AWS has resolved the underlying infrastructure issues in us-east-1. We have marked the region as healthy and are failing our AWS us-east-1 primary multi-region replication customers back and resolving.