- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-east4
- Regions
- us, us-east4
- Down Index
- 31of 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 6d 11h it lasted.
Anything that failed between 2026-07-07 13:00 UTC and 2026-07-14 00:42 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 8
- investigating
Customers in GCP us-east4 may experience elevated API latencies.
provider
- investigating
We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available.
provider
- identified
We are currently working to remediate the elevated API latencies that were observed in GCP us-east4.
provider
- identified
We are continuing to work on the investigation and remediation of the elevated API latencies in GCP us-east4. We will provide further updates within one hour.
provider
- monitoring
We have rolled out a change and have paused further investigation overnight pending validation under daytime traffic.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
The latencies were caused by issues with a downstream service which resolved after we scaled up. We've been monitoring for errors and latencies and have not seen any further issues. This issue is now considered 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-a6d03a1e64
Is Temporal Cloud still down?
No, this incident was resolved 2026-07-14 00:42 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
6d 11h, from 2026-07-07 13:00 UTC to 2026-07-14 00:42 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.