- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-east-1
- Regions
- us, us-east-1
- Down Index
- 27of 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 2h 17m it lasted.
Anything that failed between 2026-10-09 22:33 UTC and 2026-10-10 00:51 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 5
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- resolved
This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.
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-880a8e2129
Is Temporal Cloud still down?
No, this incident was resolved 2026-10-10 00:51 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
2h 17m, from 2026-10-09 22:33 UTC to 2026-10-10 00:51 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.