IBM Cloud Docs
Region and data center locations for resource deployment

Region and data center locations for resource deployment

IBM Cloud® has a resilient global network of locations to host your highly available cloud workload. You can create resources in different locations, such as a region or data center, but with the same billing and usage view. You can also deploy your apps to the location that is nearest to your customers to achieve low application latency. IBM Cloud provides three tiers of regions: multizone regionsA region that is spread across data centers in multiple zones to increase fault tolerance., single-campus multizone regionsA region that consists of multiple zones that are hosted on data centers that are located within a single building or campus. Dependencies such as power, cooling, networking, and physical security might overlap but are not identical between any two zones to increase fault tolerance., and data centersThe physical location of the servers that provide cloud services..

Regions

Multizone regions (MZRs) are composed of three or more zones that are independent from each other to ensure that single failure events affect only a single zone. MZRs provide low latency (< 2-milliseconds latency) and high bandwidth (> 1000 Gbps) connectivity across zones. For GADate when a product is widely available for sale and delivery to customers or channels, usually across multiple geographies. service rollout, see the Service rollout policy.

The advantage of an MZR is that it provides consistent cloud services across different zones, better resiliency, availability, higher interconnect speed between data centers for your resources. These features can be critical to your applications. Deploying the application in an MZR rather than a different deployment location (data centers, either physical or logical) is that you can increase the availability from 99.9% to 99.99% when deployed over three zones.

IBM® offers two types of multizone regions. The underlying infrastructure in both types provides the same SLA.

Multizone regions (MZR)

MZRs offer the highest level of redundancy and availability because it uses three separate sites within a region.

This diagram shows a geography that contains data center buildings that host a multizone region (MZR)
Figure 1. Multizone region (MZR)

The following table lists the IBM Cloud MZRs that fall into this category and the region, zone, and data center codes for each one.

Table 1. MZRs in North and South America
Use the buttons before the table to change the context of the table. The column headers identify the data centers located in the specific geographical area.
Location Region Zone Data center
Dallas us-south us-south-1
us-south-2
us-south-3
us-south-4
DAL10
DAL12
DAL13
DAL14
Sao Paulo br-sao br-sao-1
br-sao-2
br-sao-3
SAO01
SAO04
SAO05
Toronto ca-tor ca-tor-1
ca-tor-2
ca-tor-3
TOR01
TOR04
TOR05
Washington DC us-east us-east-1
us-east-2
us-east-3
WDC04
WDC06
WDC07
Table 1. MZRs in Europe
Use the buttons before the table to change the context of the table. The column headers identify the data centers located in the specific geographical area.
Location Region Zone Data center
Frankfurt eu-de eu-de-1
eu-de-2
eu-de-3
FRA02
FRA04
FRA05
London eu-gb eu-gb-1
eu-gb-2
eu-gb-3
LON04
LON05
LON06
Madrid eu-es eu-es-1
eu-es-2
eu-es-3
MAD02
MAD04
MAD05
Table 1. MZRs in Asia Pacific
Use the buttons before the table to change the context of the table. The column headers identify the data centers located in the specific geographical area.
Location Region Zone Data center
Sydney au-syd au-syd-1
au-syd-2
au-syd-3
SYD01
SYD04
SYD05
Tokyo jp-tok jp-tok-1
jp-tok-2
jp-tok-3
TOK02
TOK04
TOK05

Single campus MZRs

Single campus MZRs contain three availability zones in different sections of the same building or within multiple buildings on a campus where the power, cooling, networking, and physical security dependencies overlap but are not identical between any two availability zones. This setup ensures a level of continuous availability and survivability of any one system outage, planned or unplanned.

SLAs are maintained because the infrastructure is set up in a concurrently maintainable fashion so that a single failure does not affect all three zones in the same campus. This setup is ideal for services that support local users as it reduces latency or to support disaster recovery workloads.

This diagram shows a geography that contains a single campus MZR
Figure 2. Single campus MZR

The following table lists the single campus MZRs that are available in IBM Cloud and the region, zone, and data center codes for each one.

Table 2. Single campus MZRs
Location Region Zone Data center
Osaka jp-osa jp-osa-1
jp-osa-2
jp-osa-3
OSA21
OSA22
OSA23

OSA2X (formerly known as OSA02) is the physical data center.

Data centers

In addition to selecting a region for your resource, you can select from a list of the IBM Cloud data centers, depending on the type of resource you're working with.

Data centers host the power, cooling, compute, network, and storage resources used for services and apps. They don't provide isolation from multizones in a location.

Data centers are based on a POD architecture where each data center can have more than one POD, depending on the on-demand build out. Each POD consists of racks, servers, networks, and storage, along with backup power generators. Placing application servers across PODs improves the availability.

Global map showing MZR and data center locations
Figure 3. MZR and data center locations map

This image is an artistic representation and does not reflect actual political or geographic boundaries.

See the following table for the specific code for each data center.

Table 3. Data centers in North and South America
Use the buttons before the table to change the context of the table. The column headers identify the data centers located in the specific geographical area.
Data center Code
Dallas 05 DAL05
Dallas 08 [1] DAL08
Dallas 09 DAL09
Dallas 10 DAL10
Dallas 12 DAL12
Dallas 13 DAL13
Dallas 14 DAL14
Montreal 01 MON01
San Jose 01 SJC01
San Jose 03 SJC03
San Jose 04 SJC04
Sao Paulo 01 SAO01
Sao Paulo 04 SAO04
Sao Paulo 05 SAO05
Toronto 01 TOR01
Toronto 04 TOR04
Toronto 05 TOR05
Washington DC 01 WDC01
Washington DC 03 [2] WDC03
Washington DC 04 WDC04
Washington DC 06 WDC06
Washington DC 07 WDC07
Table 3. Data centers in Europe
Use the buttons before the table to change the context of the table. The column headers identify the data centers located in the specific geographical area.
Data center Code
Amsterdam 03 AMS03
Frankfurt 02 FRA02
Frankfurt 04 FRA04
Frankfurt 05 FRA05
London 02 LON02
London 04 LON04
London 05 LON05
London 06 LON06
Madrid 02 MAD02
Madrid 04 MAD04
Madrid 05 MAD05
Milan 01 MIL01
Paris 01 PAR01
Table 4. Data centers in Asia Pacific
Use the buttons before the table to change the context of the table. The column headers identify the data centers located in the specific geographical area.
Data center Code
Chennai 01 CHE01
Osaka 21 OSA21
Osaka 22 OSA22
Osaka 23 OSA23
Singapore 01 SNG01
Sydney 01 SYD01
Sydney 04 SYD04
Sydney 05 SYD05
Tokyo 02 TOK02
Tokyo 04 TOK04
Tokyo 05 TOK05

The table includes certain data centers that are set to close soon. For the list of data centers that are closing, see Data center closures.

Viewing resources by location

You can view all resources and locations from the Resource list page in the console. If you want to view and work with resources in a specific location, expand the Location filter, and select a location from the list. By expanding a specific location, you can select to filter by individual data centers, regions, or zones.

Depending on the type of resource, you might be interested in only specific types of location data. For example, if you created a service or VPC infrastructure service, you can filter the Resource list page by the region and zone codes. However, if you're working with classic infrastructure resources, the specific data center codes are the pertinent information for you.

For example, if you have resources that are deployed in the London 2 (eu-gb-2) zone, you can set filters to display only those resources in your resource list. Expand the London metro option, and the London (eu-gb) region option. Within that region, you can select from the list of available zones, such as London 2 (eu-gb-2). If you have a classic infrastructure resource that is deployed in a specific data center, you can identify the data center by the specific metro location and alphanumeric code. For example, use Dallas for the metro location and then Dallas 05 (dal05) for the data center.

You might also want to display your resources that are located globally. The Global option means that only one logical, globally accessible instance of the service, independent of any region or zone, is published to customer applications. These types of resources are accessible from a global endpoint.

As illustrated in the following graphic, a data center is a physical building that represents an availability zone that is located within a multizone region (MZR). An MZR is organized by its metro location. For example, London can encompass more than one grouping of data centers within an MZR. The graphic shows three availability zones in one MZR that work together in the instance that one of the data centers becomes unavailable. Availability zones are connected directly to each or through low latency links.

A location hierarchy that shows a geography that contains data center buildings inside of availability zones that are interconnected with points-of-presence within a metro.
Figure 4. Location hierarchy


  1. IBM Cloud for Government Learn more ↩︎

  2. IBM Cloud for Government Learn more ↩︎