Temporal Cloud outage, 15 October 2026

New namespace creation restricted across all GCP regions

Started
Status
Ongoing: Monitoring
Impact
Minor
Affected
Capacity

Last update from Temporal Cloud

We have temporarily restricted new Temporal Cloud namespace creation across all GCP regions due to compute capacity constraints. Existing namespaces continue to operate normally. For details, available alternatives, and how to request an exception, see https://docs.temporal.io/evaluate/cloud/regions#gcp-capacity-restriction

15 Oct 2026, 17:12 UTC

Read the full incident on the official Temporal Cloud status page

Is Temporal Cloud down now?

This page is the record of one past incident. For the live status, see Is Temporal Cloud down right now? - it reads the official status page every 2 minutes.

Other Temporal Cloud incidents

  1. Elevated latency and errors in GCP us-west1

  2. Elevated latency and errors in AWS us-east-1

  3. Elevated error rates for cross-region traffic between US AWS regions

  4. Elevated GCP storage latency in us-central1 - precautionary namespace failover

  5. Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI

  6. UI Disruptions in GCP us-central1

  7. Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors

  8. Increased latency in region us-west-2

All recorded Temporal Cloud incidents