Service regions - Temporal Cloud
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.
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.
AWS Service Regions
Temporal Cloud operates in the following Amazon Web Services (AWS) regions:
| Area | Code | Region | Notes |
|---|---|---|---|
| Asia Pacific | ap-northeast-1 | Tokyo | |
| Asia Pacific | ap-northeast-2 | Seoul | |
| Asia Pacific | ap-south-1 | Mumbai | |
| Asia Pacific | ap-south-2 | Hyderabad | |
| Asia Pacific | ap-southeast-1 | Singapore | |
| Asia Pacific | ap-southeast-2 | Sydney | |
| Europe | eu-central-1 | Frankfurt | |
| Europe | eu-west-1 | Ireland | |
| Europe | eu-west-2 | London | |
| North America | ca-central-1 | Central Canada | |
| North America | us-east-1 | Northern Virginia | |
| North America | us-east-2 | Ohio | |
| North America | us-west-2 | Oregon | |
| South America | sa-east-1 | São Paulo | Does not support Multi-region replication |
GCP Service Regions
Temporal Cloud operates the following Google Cloud (GCP) regions:
| Area | Code | Region | Notes |
|---|---|---|---|
| North America | us-central1 | Iowa | Does not support Same-region Replication |
| North America | us-west1 | Oregon | Does not support Same-region Replication |
| North America | us-east4 | Northern Virginia | Does not support Same-region Replication |
| Europe | europe-west3 | Frankfurt | Does not support Multi-region or Same-region Replication |
| Asia Pacific | asia-south1 | Mumbai | Does not support Multi-region or Same-region Replication |