Skip to main content

Service regions

You can access Temporal Cloud from anywhere with Internet connectivity, no matter where your Temporal Cloud Namespaces are physically located. Your applications can live in the cloud environment or data center of your choice. With that in mind, you will reduce latency by creating Namespaces in a region close to where you host your Workers.

This page enumerates the current regions supported by Temporal Cloud Namespaces.

Region Status

Visit status.temporal.io to check the status of our supported regions. On that page, you can also subscribe to updates to receive email notifications whenever Temporal creates, updates or resolves an incident.

Supported Regions

caution
  • While GCP Namespaces support Multi-region Replication, they do not support Same-region Replication.
  • When using Multi-region Replication, both regions must co-exist within the same continent.
  • When using Multi-region Replication, both regions must co-exist within the same provider.

AWS Service Regions

Temporal Cloud operates in the following Amazon Web Services (AWS) regions:

AreaCodeRegionNotes
Asia Pacificap-northeast-1Tokyo
Asia Pacificap-northeast-2Seoul
Asia Pacificap-south-1Mumbai
Asia Pacificap-south-2Hyderabad
Asia Pacificap-southeast-1Singapore
Asia Pacificap-southeast-2Sydney
Europeeu-central-1Frankfurt
Europeeu-west-1Ireland
Europeeu-west-2London
North Americaca-central-1Central Canada
North Americaus-east-1Northern Virginia
North Americaus-east-2Ohio
North Americaus-west-2Oregon
South Americasa-east-1São PauloDoes not support
Multi-region replication

GCP Service Regions

Temporal Cloud operates the following Google Cloud (GCP) regions:

AreaCodeRegionNotes
North Americaus-west1OregonDoes not support
Same-region Replication
North Americaus-east4Northern VirginiaDoes not support
Same-region Replication
Europeeurope-west3FrankfurtDoes not support
Multi-region or
Same-region Replication
Asia Pacificasia-south1MumbaiDoes not support
Multi-region or
Same-region Replication