# Some customers in AWS us-east-1 may experience elevated API latencies

- Provider: [Temporal Cloud](https://down.guide/providers/temporal-cloud)
- Confidence: Confirmed
- Impact: Degraded
- lasted 1d 2h
- started 2026-05-08 01:50 UTC
- us-east-1
- us, us-east-1
- id: DWN-a27efb541b
- Official page: https://stspg.io/sx6fm6kctdq3

## Updates from Temporal Cloud
### 2026-05-08 01:14 UTC: investigating
Some customers in AWS us-east-1 may experience elevated API latencies.

### 2026-05-08 01:50 UTC: identified
We have proactively failed over all impacted 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

### 2026-05-08 02:55 UTC: identified
We are continuing to work closely with AWS as they address the underlying issue. We are also actively monitoring the health of impacted namespaces.

### 2026-05-08 03:40 UTC: identified
We are continuing to work closely with AWS as they address the underlying issue and are actively monitoring impacted namespaces for stability. We have also confirmed multi-region replication-enabled namespaces are in their expected replication configuration.

### 2026-05-08 07:43 UTC: identified
We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.

### 2026-05-08 09:27 UTC: monitoring
We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable.

### 2026-05-08 12:29 UTC: monitoring
We continue to monitor the situation and the service stability has been maintained.

### 2026-05-08 17:37 UTC: monitoring
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.

### 2026-05-09 03:56 UTC: resolved
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 into this region.

From the builder: does your app depend on Temporal Cloud? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=temporal-cloud) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Temporal Cloud.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-a27efb541b), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.