- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-east4
- Regions
- us, us-east4
- Down Index
- 28of 100
What to do
Check whether you use Temporal Cloud us-east4 in us, us-east4. 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 53m it lasted.
Anything that failed between 2026-06-08 22:06 UTC and 2026-06-09 00:59 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 currently investigating this issue.
provider
- monitoring
A fix has been implemented and we are monitoring
provider
- monitoring
Multi Region Namespaces were failed over at 10:23 PM UTC
provider
- monitoring
The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in.
provider
- resolved
Namespaces have been failed back to their primary region. This incident has been 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-8404d7f2d9
Is Temporal Cloud still down?
No, this incident was resolved 2026-06-09 00:59 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
2h 53m, from 2026-06-08 22:06 UTC to 2026-06-09 00:59 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named us-east4 in us, us-east4.
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.