Skip to main content
Temporal Cloud

Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress

Partial outage Lasted 10h 30m · started · Temporal Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
us-central1, asia-southeast2
Regions
apac, asia-southeast2, us, us-central1
Down Index
49of 100

What to do

  • Check whether you use Temporal Cloud us-central1, asia-southeast2 in apac, asia-southeast2, 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 10h 30m it lasted.

    Anything that failed between 2026-09-10 20:51 UTC and 2026-09-11 07:21 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 7

  1. identified

    Some customers with namespaces in the us-central1 and asia-southeast2 regions may experience errors and blocked progress on their workflows. We are currently rolling out a fix.

    provider

  2. monitoring

    The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.

    provider

  3. monitoring

    We are continuing to monitor for any further issues.

    provider

  4. monitoring

    While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.

    provider

  5. monitoring

    We are continuing to monitor for any further issues.

    provider

  6. monitoring

    A configuration change affecting namespaces in the us-central1 and asia-southeast2 regions resulted in some workflow requests not being processed as expected. The change was rolled back and workflow processing resumed. We are continuing to validate the environment and clear any residual issues, and will provide further updates as that work completes.

    provider

  7. resolved

    The environment has been validated and all residual issues have been cleared. This incident is now 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-d2b3fd6745

Is Temporal Cloud still down?

No, this incident was resolved 2026-09-11 07:21 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.

How long did it last?

10h 30m, from 2026-09-10 20:51 UTC to 2026-09-11 07:21 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named us-central1, asia-southeast2 in apac, asia-southeast2, 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.