- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-east-1
- Regions
- us, us-east-1
- Down Index
- 31of 100
What to do
Check whether you use Temporal Cloud us-east-1 in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 2h it lasted.
Anything that failed between 2026-05-08 01:50 UTC and 2026-05-09 03:56 UTC may need a replay.Subscribe to Temporal Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=temporal-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Temporal Cloud 9
- investigating
Some customers in AWS us-east-1 may experience elevated API latencies.
provider
- 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
provider
- 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.
provider
- 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.
provider
- identified
We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.
provider
- monitoring
We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable.
provider
- monitoring
We continue to monitor the situation and the service stability has been maintained.
provider
- 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.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a27efb541b
Is Temporal Cloud still down?
No, this incident was resolved 2026-05-09 03:56 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
1d 2h, from 2026-05-08 01:50 UTC to 2026-05-09 03:56 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named us-east-1 in us, us-east-1.
What caused it?
Temporal Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Temporal Cloud's official status page, https://status.temporal.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.