Skip to main content
Temporal Cloud

Elevated GCP storage latency in us-central1 – precautionary namespace failover

Degraded Lasted 4h 25m · started · Temporal Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-central1
Down Index
29of 100

What to do

  • Check whether you use Temporal Cloud in 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 4h 25m it lasted.

    Anything that failed between 2026-10-08 21:53 UTC and 2026-10-09 02:17 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. investigating

    We are monitoring elevated Cloud Storage latency from GCP in us-central1. As a precaution, multi-region namespaces in this region have been failed over to their replica regions. No impact to workflow execution has been observed. We will fail back once GCP confirms recovery.

    provider

  2. monitoring

    Cloud Storage latency in GCP us-central1 has returned to normal levels. We are continuing to monitor the region and will begin failing multi-region namespaces back to us-central1 shortly.

    provider

  3. resolved

    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-eb03844d7d

Is Temporal Cloud still down?

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

How long did it last?

4h 25m, from 2026-10-08 21:53 UTC to 2026-10-09 02:17 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named in 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.