- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-west1
- Regions
- us, us-west1
- Down Index
- 23of 100
What to do
Check whether you use Temporal Cloud us-west1 in us, us-west1. 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 17m it lasted.
Anything that failed between 2026-10-14 13:20 UTC and 2026-10-14 13:36 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 2
- monitoring
Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once monitoring confirms the region is stable.
provider
- resolved
This incident has been resolved. The GCP us-west1 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-a7eabfc7f1
Is Temporal Cloud still down?
No, this incident was resolved 2026-10-14 13:36 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
17m, from 2026-10-14 13:20 UTC to 2026-10-14 13:36 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named us-west1 in us, us-west1.
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.