Skip to main content
Temporal Cloud

Some customers using cloud ops API may experience higher latency and elevated rate of API errors

Degraded Lasted 30m · started · Temporal Cloud's page

Level
confirmed
Worst impact
Degraded
Components
Cloud Ops API
Down Index
17of 100

What to do

  • Check whether you use Temporal Cloud Cloud Ops API. 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 30m it lasted.

    Anything that failed between 2026-03-11 23:23 UTC and 2026-03-11 23:53 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

  1. identified

    Some customers using cloud ops API may experience higher latency and elevated rate of API errors

    provider

  2. monitoring

    A fix has been deployed and we will continue to monitor

    provider

  3. resolved

    This incident is 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-694ac2c69f

Is Temporal Cloud still down?

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

How long did it last?

30m, from 2026-03-11 23:23 UTC to 2026-03-11 23:53 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named Cloud Ops API.

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.