- Level
- confirmed
- Worst impact
- Partial outage
- Components
- us-east-2
- Regions
- us, us-east-2
- Down Index
- 39of 100
What to do
Check whether you use Temporal Cloud us-east-2 in us, us-east-2. 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 4h 19m it lasted.
Anything that failed between 2026-07-15 16:55 UTC and 2026-07-15 21:15 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 7
- investigating
Customers with namespaces in us-east-2 may experience errors with visibility queries. We are currently investigating.
provider
- identified
We are working on a fix, if your namespace are MRN enabled please fail over to your passive regions for faster recovery.
provider
- identified
All MRN-enabled namespaces have been failed over as of 17:53 UTC. Mitigation continues to progress.
provider
- identified
Mitigation is still in progress. We are scaling up service to help with mitigation efforts.
provider
- monitoring
Mitigation is in effect, we are seeing some recovery. Please submit a support ticket if you are seeing service degradation.
provider
- monitoring
We are seeing full recovery on our end, we are continuing to monitor.
provider
- resolved
All MRN-enabled namespaces failed over by Temporal have been failed back. This incident has been fully mitigated and is now resolved.
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-4e18105b4e
Is Temporal Cloud still down?
No, this incident was resolved 2026-07-15 21:15 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
4h 19m, from 2026-07-15 16:55 UTC to 2026-07-15 21:15 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named us-east-2 in us, us-east-2.
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.