Skip to main content
Temporal Cloud

Intermittent request failures for some namespaces in GCP us-east4

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

Level
confirmed
Worst impact
Degraded
Components
us-east4
Regions
us, us-east4
Down Index
25of 100

What to do

  • Check whether you use Temporal Cloud us-east4 in us, us-east4. 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 45m it lasted.

    Anything that failed between 2026-10-31 13:31 UTC and 2026-10-31 14:16 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 4

  1. investigating

    We are investigating intermittent request failures affecting a subset of namespaces in GCP. Affected users may see elevated latency and error rates on API calls, including worker polling (workflow, activity, and Nexus tasks), which can result in reduced task throughput.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. monitoring

    We are continuing to monitor for any further issues.

    provider

  4. 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-3e4605bae3

Is Temporal Cloud still down?

No, this incident was resolved 2026-10-31 14:16 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.

How long did it last?

45m, from 2026-10-31 13:31 UTC to 2026-10-31 14:16 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named us-east4 in us, us-east4.

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.