- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-central1
- Down Index
- 23of 100
What to do
Check whether you use Temporal Cloud 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 17m it lasted.
Anything that failed between 2026-04-09 00:30 UTC and 2026-04-09 00:47 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
- resolved
From 2026-04-09 00:23:00 UTC to 2026-04-09 00:47:15 UTC, some customers using GCP private service connect in us-central1 may have had client connection issues or UNAVAILABLE responses
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-b962a9c0f2
Is Temporal Cloud still down?
No, this incident was resolved 2026-04-09 00:47 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
17m, from 2026-04-09 00:30 UTC to 2026-04-09 00:47 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named 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.