- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-central1
- Regions
- us, us-central1
- Down Index
- 29of 100
What to do
Check whether you use Temporal Cloud us-central1 in 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 5h 56m it lasted.
Anything that failed between 2026-09-01 15:47 UTC and 2026-09-01 21:43 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 3
- investigating
We are currently investigating elevated error rates in GCP us-central1, and have failed over MRN namespaces in this region.
provider
- identified
We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
provider
- resolved
GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.
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-e7a4c20485
Is Temporal Cloud still down?
No, this incident was resolved 2026-09-01 21:43 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
5h 56m, from 2026-09-01 15:47 UTC to 2026-09-01 21:43 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named us-central1 in 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.