
Temporal Status
Real-time updates of Temporal issues and outages
Temporal status is Operational
us-east-1
Capacity
Active Incidents
No active incidents
Recently Resolved Incidents
We have temporarily restricted new Temporal Cloud namespace creation across few GCP regions due to compute capacity constraints. Impacted regions are us-central1 and europe-west3. 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
Customers in us-east-1 may experience elevated latency in the Visibility API and delays in workflow updates being reflected in the API.
Temporal Outage Survival Guide
You're checking on Temporal - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Temporal Components
Temporal Amazon Web Services (AWS)
ap-northeast-1
ap-northeast-2
ap-south-1
ap-south-2
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-west-1
eu-west-2
sa-east-1
us-east-1
Customers in us-east-1 may experience elevated latency in the Visibility API and delays in workflow updates being reflected in the API.
us-east-2
us-west-2
Capacity
Temporal Google Cloud Platform (GCP)
asia-south1
australia-southeast1
europe-west3
us-east4
us-central1
us-west1
asia-southeast2
Capacity
We have temporarily restricted new Temporal Cloud namespace creation across few GCP regions due to compute capacity constraints. Impacted regions are us-central1 and europe-west3. 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