Some workloads running in Google Cloud require low latency between their virtual machine (VM) instances in a specified region and the Dedicated Interconnect colocation facility that you choose. If this is true for your workloads, you can select a low-latency (< 5 milliseconds) colocation facility location from the Locations table in this document.
The pricing for low-latency locations is the same as for all other locations.
If your workloads don't require low-latency connectivity, you can use any of our colocation facilities locations.
Requirements and recommendations
For Dedicated Interconnect, your network must physically meet Google's network in a supported colocation facility, also known as an Interconnect connection location. This facility is where a vendor, the colocation facility provider, provisions a circuit between your network and a Google Edge point of presence (PoP).
For more information, see the Dedicated Interconnect overview.
In the Locations table, the Region served column
indicates the regions in which you can create VLAN attachments, which affect
latency and egress costs. For example, if you have VMs
in region us-east4 (Virginia), you might create a
Dedicated Interconnect connection in Ashburn and then create a
VLAN attachment in us-east4. Your traffic then doesn't have to travel
far to move between your VMs and the Dedicated Interconnect
connection, which results in lower latency than, for example, creating a
Dedicated Interconnect connection and a VLAN attachment in Europe.
Also, it's more cost-effective to create VLAN attachments in the same regions as your VMs because you don't have to pay inter-region egress costs when VMs send traffic to your on-premises network.
Other Google Cloud location options
For other location options, such as network edge locations or Cloud CDN locations, see Choosing a product.
Locations table
The following table lists low-latency locations where you can create
Dedicated Interconnect connections. The locations are organized
by the Google Cloud regions served, metropolitan area, and then by
edge availability domain (metro availability zone). The name of each
location indicates its edge availability domain, such as the zone1 in
iad-zone1-1.
To list locations, you can
also use the Google Cloud Console or the gcloud command-line tool.
| Region served | Metropolitan area | Interconnect location name with < 5 ms to region | Facility provider |
|---|---|---|---|
|
| Montreal | yul-zone1-1944 | Cologix MTL3 |
| Montreal | yul-zone2-1944 | Cologix MTL3 | |
|
| Toronto | yyz-zone1-392 | Equinix Toronto (TR1) |
| Toronto | yyz-zone2-2206 | Equinix Toronto (TR2) | |
|
|
Ashburn | iad-zone1-1 | Equinix Ashburn (DC1-DC11) |
| Ashburn | iad-zone2-1 | Equinix Ashburn (DC1-DC11) | |
| Ashburn | iad-zone1-5467 | CoreSite - Reston (VA3) | |
| Ashburn | iad-zone2-5467 | CoreSite - Reston (VA3) | |
|
|
Council Bluffs | cbf-zone1-575 | Nebraska data centers (1623 Farnam) |
| Council Bluffs | cbf-zone2-575 | Nebraska data centers (1623 Farnam) | |
|
|
Portland | pdx-zone1-1922 | EdgeConneX Portland (EDCPOR01) |
| Portland | pdx-zone2-1922 | EdgeConneX Portland (EDCPOR01) | |
|
|
Los Angeles | lax-zone1-8 | Equinix Los Angeles (LA1) |
| Los Angeles | lax-zone2-19 | CoreSite - LA1 - One Wilshire | |
|
|
Helsinki | hem-zone1-7098 | Equinix HE7 Helsinki Sinimäki |
| Helsinki | hem-zone2-7098 | Equinix HE7 Helsinki Sinimäki | |
| Helsinki | hem-zone1-8128 | Telia Helsinki Datacenter | |
| Helsinki | hem-zone2-8128 | Telia Helsinki Datacenter | |
|
|
London | lhr-zone1-47 | Global Switch (London 2) |
| London | lhr-zone2-47 | Global Switch (London 2) | |
| London | lhr-zone1-832 | Equinix London Slough (LD5-LD6) | |
| London | lhr-zone2-832 | Equinix London Slough (LD5-LD6) | |
|
| Frankfurt | fra-zone1-58 | Interxion Frankfurt |
| Frankfurt | fra-zone1-277 | e-shelter Frankfurt (FRA1) | |
| Frankfurt | fra-zone1-683 | Equinix Frankfurt West (FR4) | |
| Frankfurt | fra-zone2-58 | Interxion Frankfurt | |
| Frankfurt | fra-zone2-277 | e-shelter Frankfurt (FRA1) | |
| Frankfurt | fra-zone2-683 | Equinix Frankfurt West (FR4) | |
|
|
Amsterdam | ams-zone1-1236 | Equinix Amsterdam Schepenbergweg (AM5) (formerly Telecity AMS5) |
| Amsterdam | ams-zone2-1320 | Equinix Amsterdam (AM3) | |
|
|
Zurich | zrh-zone1-81 | Interxion Zurich / Glattbrugg |
| Zurich | zrh-zone2-81 | Interxion Zurich / Glattbrugg | |
| Zurich | zrh-zone1-1086 | greenDatacenter Lupfig | |
| Zurich | zrh-zone2-1086 | greenDatacenter Lupfig | |
|
|
Taipei | tsa-zone1-456 | Chief Telecom |
| Taipei | tsa-zone2-2886 | CHT Taipei-Aikuo IDC | |
|
|
Hong Kong | hkg-zone1-225 | MEGA-i (iAdvantage Hong Kong) |
| Hong Kong | hkg-zone2-1118 | Equinix Hong Kong (HK2) | |
|
|
Tokyo | nrt-zone1-599 | ComSpace I |
| Tokyo | nrt-zone1-452 | Equinix Tokyo (TY2) | |
| Tokyo | nrt-zone2-452 | Equinix Tokyo (TY2) | |
| Tokyo | nrt-zone1-738 | AT TOKYO | |
| Tokyo | nrt-zone2-738 | AT TOKYO | |
|
|
Singapore | sin-zone1-388 | Global Switch Singapore |
| Singapore | sin-zone2-2260 | Equinix Singapore (SG3) | |
|
|
Mumbai | bom-zone1-2310 | GPX Mumbai |
| Mumbai | bom-zone2-554 | Tata Mumbai IDC | |
|
|
Sydney | syd-zone1-1660 | NEXTDC S1 |
| Sydney | syd-zone2-1605 | Equinix Sydney (SY3) |
|
| Melbourne | mel-zone1-1988 | Equinix ME1/ME2 - Melbourne | |
| Melbourne | mel-zone2-1988 | Equinix ME1/ME2 - Melbourne | |
| Melbourne | mel-zone1-4843 | NEXTDC M2 | |
| Melbourne | mel-zone2-4843 | NEXTDC M2 | |
|
|
Sao Paulo | gru-zone1-1057 | Global Crossing São Paulo |
| Sao Paulo | gru-zone2-1057 | Global Crossing São Paulo | |
| Sao Paulo | gru-zone1-165 | Equinix São Paulo (SP4) | |
| Sao Paulo | gru-zone2-165 | Equinix São Paulo (SP4) | |
| Sao Paulo | gru-zone1-7580 | Ascenty - Sao Paulo 2 | |
| Sao Paulo | gru-zone2-7580 | Ascenty - Sao Paulo 2 | |
|
|
|||
| Santiago | scl-zone1-1779 | Level(3) Santiago | |
| Santiago | scl-zone2-1779 | Level(3) Santiago |