- Level
- confirmed
- Worst impact
- Degraded
- Components
- Capacity
- Regions
- eu, europe-west3, us, us-central1, us-east4
- Down Index
- 43of 100
What to do
Check whether you use Temporal Cloud Capacity in eu, europe-west3, us, us-central1. 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 0m it lasted.
Anything that failed between 2026-10-15 17:12 UTC and 2026-10-15 17:12 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 1
- monitoring
We have temporarily restricted new Temporal Cloud namespace creation across few GCP regions due to compute capacity constraints. Impacted regions are us-central1, us-east4 and europe-west3. Existing namespaces continue to operate normally. For details, available alternatives, and how to request an exception, see https://docs.temporal.io/evaluate/cloud/regions#gcp-capacity-restriction
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-e9f290baf4
Is Temporal Cloud still down?
No, this incident was resolved 2026-10-15 17:12 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
0m, from 2026-10-15 17:12 UTC to 2026-10-15 17:12 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named Capacity in eu, europe-west3, us, us-central1.
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.