- Level
- confirmed
- Worst impact
- Degraded
- Components
- europe-west3
- Regions
- eu, europe-west3
- Down Index
- 23of 100
What to do
Check whether you use Temporal Cloud europe-west3 in eu, europe-west3. 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 22m it lasted.
Anything that failed between 2026-04-21 23:15 UTC and 2026-04-21 23:37 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
- investigating
We are investigating an issue where child workflows started with the TerminateIfRunning conflict policy may fail to start. The issue began approximately 2026-04-21 19:39 UTC.A fix is in progress and we will provide updates shortly.
provider
- resolved
We identified and resolved an issue that caused some Child Workflows to fail to start under certain conditions. Affected Workflows have been reprocessed and are now operating normally as of 23:26 UTC.
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-ba3c85c9ea
Is Temporal Cloud still down?
No, this incident was resolved 2026-04-21 23:37 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
22m, from 2026-04-21 23:15 UTC to 2026-04-21 23:37 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named europe-west3 in eu, europe-west3.
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.