For the complete documentation index, see /llms.txt. This page is also available as raw Markdown at /evaluate/cloud/regions.md. Append .md to any page URL to fetch its Markdown.

Service regions

View Markdown

You can reach Temporal Cloud from anywhere with Internet connectivity, wherever your Namespaces are located, and your applications can run in the cloud environment or data center of your choice. Create Namespaces in a region close to where you host your Workers to reduce latency.

This page lists the regions where you can create a Temporal Cloud Namespace.

Service availability

Check the status of supported regions at status.temporal.io. Subscribe there to get an email whenever Temporal creates, updates, or resolves an incident.

AWS service regions

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

Asia Pacific - Tokyo (ap-northeast-1)

• Cloud API Code: aws-ap-northeast-1
• Regional Endpoint: ap-northeast-1.aws.api.temporal.io:7233
• PrivateLink Endpoint Service: com.amazonaws.vpce.ap-northeast-1.vpce-svc-08f34c33f9fb8a48a
• Same Region Replication: Not Available
• Multi-Region Replication:
  • aws-ap-northeast-2
  • aws-ap-south-1
  • aws-ap-south-2
  • aws-ap-southeast-1
  • aws-ap-southeast-2
• Multi-Cloud Replication:
  • gcp-asia-south1

Asia Pacific - Seoul (ap-northeast-2)

• Cloud API Code: aws-ap-northeast-2
• Regional Endpoint: ap-northeast-2.aws.api.temporal.io:7233
• PrivateLink Endpoint Service: com.amazonaws.vpce.ap-northeast-2.vpce-svc-08c4d5445a5aad308
• Same Region Replication: Not Available
• Multi-Region Replication:
  • aws-ap-northeast-1
  • aws-ap-south-1
  • aws-ap-south-2
  • aws-ap-southeast-1
  • aws-ap-southeast-2
• Multi-Cloud Replication:
  • gcp-asia-south1

Asia Pacific - Mumbai (ap-south-1)

• Cloud API Code: aws-ap-south-1
• Regional Endpoint: ap-south-1.aws.api.temporal.io:7233
• PrivateLink Endpoint Service: com.amazonaws.vpce.ap-south-1.vpce-svc-0ad4f8ed56db15662
• Same Region Replication: Not Available
• Multi-Region Replication:
  • aws-ap-northeast-1
  • aws-ap-northeast-2
  • aws-ap-south-2
  • aws-ap-southeast-1
  • aws-ap-southeast-2
• Multi-Cloud Replication:
  • gcp-asia-south1

Asia Pacific - Hyderabad (ap-south-2)

• Cloud API Code: aws-ap-south-2
• Regional Endpoint: ap-south-2.aws.api.temporal.io:7233
• PrivateLink Endpoint Service: com.amazonaws.vpce.ap-south-2.vpce-svc-08bcf602b646c69c1
• Same Region Replication: Not Available
• Multi-Region Replication:
  • aws-ap-northeast-1
  • aws-ap-northeast-2
  • aws-ap-south-1
  • aws-ap-southeast-1
  • aws-ap-southeast-2
• Multi-Cloud Replication:
  • gcp-asia-south1

Asia Pacific - Singapore (ap-southeast-1)

• Cloud API Code: aws-ap-southeast-1
• Regional Endpoint: ap-southeast-1.aws.api.temporal.io:7233
• PrivateLink Endpoint Service: com.amazonaws.vpce.ap-southeast-1.vpce-svc-05c24096fa89b0ccd
• Same Region Replication: Not Available
• Multi-Region Replication:
  • aws-ap-northeast-1
  • aws-ap-northeast-2
  • aws-ap-south-1
  • aws-ap-south-2
  • aws-ap-southeast-2
• Multi-Cloud Replication:
  • gcp-asia-south1

Asia Pacific - Sydney (ap-southeast-2)

• Cloud API Code: aws-ap-southeast-2
• Regional Endpoint: ap-southeast-2.aws.api.temporal.io:7233
• PrivateLink Endpoint Service: com.amazonaws.vpce.ap-southeast-2.vpce-svc-0634f9628e3c15b08
• Same Region Replication: Available
• Multi-Region Replication:
  • aws-ap-northeast-1
  • aws-ap-northeast-2
  • aws-ap-south-1
  • aws-ap-south-2
  • aws-ap-southeast-1
• Multi-Cloud Replication:
  • gcp-asia-south1

Europe - Frankfurt (eu-central-1)

• Cloud API Code: aws-eu-central-1
• Regional Endpoint: eu-central-1.aws.api.temporal.io:7233
• PrivateLink Endpoint Service: com.amazonaws.vpce.eu-central-1.vpce-svc-073a419b36663a0f3
• Same Region Replication: Not Available
• Multi-Region Replication:
  • aws-eu-west-1
  • aws-eu-west-2
• Multi-Cloud Replication: