Stay organized with collections
Save and categorize content based on your preferences.
When you order a Dedicated Interconnect connection, you must specify a
colocation facility where your network meets Google's network. In most cases,
select a facility that's geographically close to your on-premises network.
To use the Google Cloud console or Google Cloud CLI to view a list of facilities,
see the following steps.
Permissions required for this task
To perform this task, you must have been granted the following permissions
or the following Identity and Access Management (IAM) roles.
Permissions
compute.interconnectLocations.list
compute.interconnectLocations.get
Roles
roles/owner
roles/editor
roles/compute.networkAdmin
Console
You can view a list of the colocation facilities when you order a
Dedicated Interconnect connection. You can filter the locations by city or
facility name.
NAME DESCRIPTION FACILITY_PROVIDER
lhr-zone1-832 Equinix London Slough (LD5) Equinix
nrt-zone1-599 ComSpace I Marubeni Access Solutions Inc.
nrt-zone2-452 Equinix Tokyo (TY2) Equinix
...
Describe a location by providing a name to view the details of a facility,
such as their physical address. The following example describes the
lhr-zone1-832 location:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# List locations\n\nWhen you order a Dedicated Interconnect connection, you must specify a\ncolocation facility where your network meets Google's network. In most cases,\nselect a facility that's geographically close to your on-premises network.\n\nTo view a list of these facilities in the documentation, see\n[All colocation facilities](/network-connectivity/docs/interconnect/concepts/choosing-colocation-facilities).\n\nTo use the Google Cloud console or Google Cloud CLI to view a list of facilities,\nsee the following steps.\n\n#### Permissions required for this task\n\nTo perform this task, you must have been granted the following permissions\n*or* the following Identity and Access Management (IAM) roles.\n\n**Permissions**\n\n- `compute.interconnectLocations.list`\n- `compute.interconnectLocations.get`\n\n**Roles**\n\n- `roles/owner`\n- `roles/editor`\n- `roles/compute.networkAdmin` \n\n### Console\n\nYou can view a list of the colocation facilities when you order a\nDedicated Interconnect connection. You can filter the locations by city or\nfacility name.\n\nFor more information, see\n[Ordering a Dedicated Interconnect connection](/network-connectivity/docs/interconnect/how-to/dedicated/ordering-dedicated-interconnect).\n\n### gcloud\n\nList all the colocation facilities:\n\n\u003cbr /\u003e\n\n```\n gcloud compute interconnects locations list\n \n```\n\n\u003cbr /\u003e\n\nOutput: \n\n```\n NAME DESCRIPTION FACILITY_PROVIDER\n lhr-zone1-832 Equinix London Slough (LD5) Equinix\n nrt-zone1-599 ComSpace I Marubeni Access Solutions Inc.\n nrt-zone2-452 Equinix Tokyo (TY2) Equinix\n ...\n \n```\n\n\u003cbr /\u003e\n\nDescribe a location by providing a name to view the details of a facility,\nsuch as their physical address. The following example describes the\n`lhr-zone1-832` location:\n\n\u003cbr /\u003e\n\n```\n gcloud compute interconnects locations describe lhr-zone1-832\n \n```\n\n\u003cbr /\u003e\n\nOutput: \n\n```\n address: |-\n Equinix\n 8 Buckingham Avenue\n SLOUGH\n SL1 4AX\n United Kingdom\n availabilityZone: zone1\n availableFeatures:\n − IF_MACSEC\n availableLinkTypes:\n − LINK_TYPE_ETHERNET_10G_LR\n − LINK_TYPE_ETHERNET_100G_LR\n city: London\n continent: EUROPE\n creationTimestamp: '1969-12-31T16:00:00.000-08:00'\n description: Equinix London Slough (LD5)\n facilityProvider: Equinix\n facilityProviderFacilityId: LD5\n id: '1024'\n kind: compute#interconnectLocation\n name: lhr-zone1-832\n peeringdbFacilityId: '832'\n regionInfos:\n region: https://www.googleapis.com/compute/projects/test-project/regions/europe-west1\n selfLink: https://www.googleapis.com/compute/projects/test-project/global/interconnectLocations/lhr-zone1-832\n status: AVAILABLE\n \n```\n\n\u003cbr /\u003e\n\nWhat's next\n-----------\n\n- To create a Dedicated Interconnect connection, see the\n [Dedicated Interconnect provisioning overview](/network-connectivity/docs/interconnect/how-to/dedicated/provisioning-overview).\n\n- To learn more about Cloud Interconnect options, see the\n [Cloud Interconnect overview](/network-connectivity/docs/interconnect/concepts/overview).\n\n- To help you solve common issues that you might encounter when using\n Cloud Interconnect, see\n [Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting)."]]
