- Level
- confirmed
- Worst impact
- Degraded
- Regions
- apac, asia-south1, eu, europe-west3, us, us-central1, us-east-1, us-east4, us-west-2, us-west1
- Down Index
- 43of 100
What to do
Check whether you use Temporal Cloud in apac, asia-south1, 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 13d 20h it lasted.
Anything that failed between 2026-06-03 00:45 UTC and 2026-06-16 21:08 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 20
- investigating
We are investigating a few reports where a workflow or activity is becoming stuck and not making progress when it should. Please report any such issues you see to support.
provider
- investigating
We are continuing to investigate this issue. Please report any stuck workflows or activities to support so we can help unblock them as we work on root cause investigation and resolution.
provider
- investigating
We are investigating a recent update that could have caused intermittent missed task dispatches, resulting in some tasks being stuck. Impact identified as of now is limited to a handful of workflows that were caught in a rare edge case. We will continue to share more updates as investigation progresses.
provider
- investigating
We're rolling back the recent update as a possible mitigation to avoid any further occurrences of this issue. We are however still in the process of investigating root cause and will post updates as we have them.
provider
- identified
A bug in the recent update in History pagination caused a rare edge case where an extra task could be added before the response was returned. This incorrectly advanced the read level, causing some tasks to be skipped. We’ve identified the issue, and are currently rolling back the update to stop this from happening again. We will be refreshing all executions in cells where the update was deployed and will monitor these closely. This will progress any stuck workflows, but will not impact any of the closed ones.
provider
- identified
Rollback is still in progress and we are continuing to monitor the situation.
provider
- identified
The rollback is making progress across impacted cells, and we are continuing to monitor the situation.
provider
- identified
Rollback is complete; refresh of open workflows is underway to unblock impacted workflows.
provider
- identified
Refreshes are still in progress and we are monitoring the situation.
provider
- identified
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
provider
- monitoring
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
provider
- monitoring
We are continuing to monitor the ongoing refresh process for all open workflows. We are also considering options for refreshing closed workflows. We will continue to share more updates as this progresses.
provider
- monitoring
As refresh of closed workflows progresses, some users may see unblocked stuck parent workflows from closed child workflows; this is happening because the missed task for closed child workflows is refreshed and delivered to parent. It could also happen on other stuck workflows that are waiting for task updates which were missed due to this incident.
provider
- monitoring
Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete.
provider
- monitoring
Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved.
provider
- monitoring
Refresh operations across both open and closed workflows are complete in most regions; we continue to make steady progress across the remaining few namespaces in the us-east-1, us-west-2, us-east4, us-west1, us-central1, asia-south1, europe-west3. No additional impact has been observed since mitigation was implemented, and we continue to closely monitor the environment. The next update will be provided once the refresh process has completed.
provider
- monitoring
The last few namespaces are still refreshing. We are starting to patch the code, and are monitoring the situation.
provider
- monitoring
Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
provider
- monitoring
Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
provider
- resolved
This incident has been resolved.
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-6cda9d6ea9
Is Temporal Cloud still down?
No, this incident was resolved 2026-06-16 21:08 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
13d 20h, from 2026-06-03 00:45 UTC to 2026-06-16 21:08 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named in apac, asia-south1, 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.