IBM Cloud® regions

IBM Power Virtual Server in IBM data center

The following table displays the appropriate region for your workspace:

The network round-trip latency, also known as round-trip time (RTT), is approximately 0.4 milliseconds when your workloads are running in Power Virtual Server and IBM Cloud Virtual Private Cloud (VPC), which are colocated in the same zone and connected through IBM Cloud Transit Gateway. RTT statistics might vary and are intended to help you plan the optimal placement of your cloud deployment.

Power Virtual Server regions and zones in Americas
Location VPC region[1] Power Virtual Server region VPC zone Power Virtual Server zone Classic infrastructure[2]
Dallas us-south us-south x
x
us-south-1
us-south-2
us-south-3
us-south-3 [3]		 x
x
dal10
dal12
us-south
dal14 		dal08[4]
dal09
dal10
dal12
dal13
dal14
Montreal ca-mon mon x mon01 mon01
San Jose x
x 		x
x 		x
x 		x
x 		sjc03
sjc04
Sao Paulo br-sao sao br-sao-1
br-sao-2
br-sao-3 		sao01
sao04
sao05 		sao01
sao04
sao05
Toronto ca-tor tor ca-tor-1
ca-tor-2
ca-tor-3 		tor01[5]
tor04
tor05 		tor01
tor04
tor05
Washington DC us-east us-east x
us-east-1
us-east-2
us-east-3 		x
us-east
wdc06
wdc07 		wdc03[6]
wdc04
wdc06
wdc07
Power Virtual Server regions and zones in Europe
Location VPC region[7] Power Virtual Server region VPC zone Power Virtual Server zone Classic infrastructure[8]
Amsterdam x x x x ams03
Frankfurt eu-de eu-de eu-de-1
eu-de-2
eu-de-3 		x
eu-de-1
eu-de-2 		fra02
fra04
fra05
London eu-gb lon eu-gb-1
eu-gb-2
eu-gb-3 		lon04
x
lon06 		lon02
lon04
lon05
lon06
Madrid eu-es mad eu-es-1
eu-es-2
eu-es-3 		mad02
mad04
x 		mad02
mad04
mad05
Milan x x x x mil01
Paris x x x x par01
Power Virtual Server regions and zones in Asia Pacific
Location VPC region[9] Power Virtual Server region VPC zone Power Virtual Server zone Classic infrastructure[10]
Chennai x in-che x che01 [11] che01
Chennai in-che in-che in-che-1
in-che-2
in-che-3 		x
che02
che03 		x
x
x
Osaka jp-osa osa jp-osa-1
jp-osa-2
jp-osa-3 		osa21
x
x 		osa21
osa22
osa23
Singapore x x x x sng01
Sydney au-syd syd au-syd-1
au-syd-2
au-syd-3 		x
syd04
syd05 		syd01
syd04
syd05
Tokyo jp-tok tok jp-tok-1
jp-tok-2
jp-tok-3 		x
tok04
x 		tok02
tok04
tok05

x - Not available

If you plan to create an application that uses both VPC and Power Virtual Server, review the zone mapping of your account. For example, create your VPC resources first, and then use the zone mapping to identify the universal zone for the VPC resources. This approach allows you to create the classic infrastructure resources in the same physical location. Classic infrastructure and IBM® Power® Virtual Server identify service locations by data center, while VPC identifies physical locations by universal zone name.

When you create a workspace by using the Terraform resource ibm_resource_instance or the CLI command ibmcloud resource service-instance-create, for the service name field use the value power-iaas for IBM Power Virtual Server in IBM data center and for the plan name field use the value power-virtual-server-group or power-virtual-server-private-group for IBM Power Virtual Server Private Cloud in Client location.

  1. For more information about the IBM Cloud regions that support VPC, see Creating a VPC in a different region. ↩︎

  2. For more information about the list of classic data centers in IBM Cloud, see Classic data centers. ↩︎

  3. IBM Cloud maps the VPC zone names by account and uses the universal zone names. For more information about the zone mapping by account, see Zone mapping per account and the tip after the table. ↩︎

  4. IBM Cloud for government. Learn more. ↩︎

  5. This is a single data center for the location. ↩︎

  6. IBM Cloud for government. Learn more. ↩︎

  7. For more information about the IBM Cloud regions that support VPC, see Creating a VPC in a different region. ↩︎

  8. For more information about the list of classic data centers in IBM Cloud, see Classic data centers. ↩︎

  9. For more information about the IBM Cloud regions that support VPC, see Creating a VPC in a different region. ↩︎

  10. For more information about the list of classic data centers in IBM Cloud, see Classic data centers. ↩︎

  11. This is a single data center for the location. ↩︎