Metros

Equinix Metal™ Metros are facilities that are grouped together geographically and share capacity and networking features. Our metros span Equinix IBX facilities in the Americas, Europe and Middle-East, Asia-Pacific regions.

Provisioning within a Metro

When you provision servers on Equinix Metal, you select the Metro where you want it to live. We determine which specific IBX within the Metro your server physically resides in based on a variety of factors including the capacity of the Metro and the entitlements of your account or organization.

Console

When you provision a new on demand server, selecting a Metro is the first choice you make.

CLI

When you use the metal device create command, use the --metro or -m parameter to specify the Metro.

metal device create -p $METAL_PROJECT_ID -P <plan> -m <metro> -H <hostname> -O <operating_system>

API

When you send the provisioning POST request projects/{id}/devices endpoint, use the "metro" field with the metro_code where you want the server to live.

curl -X POST \
-H "Content-Type: application/json" \
-H "X-Auth-Token: <API_TOKEN>" \
"https://api.equinix.com/metal/v1/projects/{id}/devices" \
-d '{
    "metro": "<metro_code>",
    "plan": "<server_type>",
    "operating_system": "<os_code>"
}'

For the ways you can check inventory and monitor capacity, see the Inventory and Capacity page.

Metro-level Networking

All of Equinix Metal's IBX locations in a Metro are interconnected by high-speed links with typical latency within less than 5 milliseconds in a Metro and there is no billing of traffic between IBXs within a Metro.

Additionally, many of our Networking features are designed to take advantage of this.

• VLANs - When you provision a VLAN in a Metro, all servers in that Metro are able to connect to it.
• Reserved Public IPv4 Addresses - When you request a public IPv4 address, you will be able to assign it to any server in the Metro where you requested it.
• Private IPv4 Addresses - All servers within a project in the same Metro can use private IPv4 addresses to connect to each other. If you need to set up connections between servers in different Metros, you can use Backend Transfer.

One thing to note about the Equinix Metal network in a Metro -- because of it's highly connected design, IBX-level server diversity does not guarantee high-availability. High-availability and redundant architectures should span multiple metros. More information is on the Location Diversity and Resilience page.

Metros Quick Reference

Tables

Americas

Region	Country	Metro	Code
AMER	Brazil	São Paulo	SP
AMER	Canada	Montreal	MT
AMER	Canada	Toronto	TR
AMER	Mexico	Mexico City	MX
AMER	United States	Atlanta	AT
AMER	United States	Chicago	CH
AMER	United States	Dallas	DA
AMER	United States	Los Angeles	LA
AMER	United States	Miami	MI
AMER	United States	New York	NY
AMER	United States	Seattle	SE
AMER	United States	Silicon Valley	SV
AMER	United States	Washington DC	DC

Europe and Middle-East

Region	Country	Metro	Code
EMEA	Finland	Helsinki	HE
EMEA	France	Paris	PA
EMEA	Germany	Frankfurt	FR
EMEA	Ireland	Dublin	DB
EMEA	Italy	Milan	ML
EMEA	Netherlands	Amsterdam	AM
EMEA	Spain	Madrid	MD
EMEA	Sweden	Stockholm	SK
EMEA	United Kingdom	London	LD
EMEA	United Kingdom	Manchester	MA

Asia-Pacific

Region	Country	Metro	Code
APAC	Australia	Melbourne	ME
APAC	Australia	Sydney	SY
APAC	Hong Kong	Hong Kong	HK
APAC	India	Mumbai	MB
APAC	Japan	Osaka	OS
APAC	Japan	Tokyo	TY
APAC	Korea	Seoul	SL
APAC	Singapore	Singapore	SG

CLI

You can list the available metros using the metal metros command.

metal metros get

Example response (truncated):

+--------------------------------------+----------------+------+
|                  ID                  |      NAME      | CODE |
+--------------------------------------+----------------+------+
| b8ffa6c9-3da2-4cf1-b48d-049002b208fe | Seattle        | se   |
| 96a57b6d-c62c-41b5-ab8e-f8d63a7f9887 | Washington DC  | dc   |
| d50fd052-34ec-4977-a173-ad6f9266995d | Hong Kong      | hk   |
| 108b2cfb-246b-45e3-885a-bf3e82fce1a0 | Amsterdam      | am   |
| 932eecda-6808-44b9-a3be-3abef49796ef | New York       | ny   |
|....                                  |....            |....  |
+--------------------------------------+----------------+------+

API

Sending a GET request to the /locations/metros endpoint returns a list of Metros available to your user account.

curl -X GET -H 'X-Auth-Token: <API_TOKEN>' https://api.equinix.com/metal/v1/locations/metros

Example response (truncated):

{
"metros": [
    {
    "id": "96a57b6d-c62c-41b5-ab8e-f8d63a7f9887",
    "name": "Washington DC",
    "code": "dc",
    "country": "US"
    },
    {
    "id": "d50fd052-34ec-4977-a173-ad6f9266995d",
    "name": "Hong Kong",
    "code": "hk",
    "country": "HK"
    },
    {
    "id": "108b2cfb-246b-45e3-885a-bf3e82fce1a0",
    "name": "Amsterdam",
    "code": "am",
    "country": "NL"
    },
    {
    "id": "932eecda-6808-44b9-a3be-3abef49796ef",
    "name": "New York",
    "code": "ny",
    "country": "US"
    },
    {
    "id": "5f72cbf6-96e4-44f2-ae60-213888fa2b9f",
    "name": "Tokyo",
    "code": "ty",
    "country": "JP"
    },
    ....
]
}    

Sending a GET request to the /locations/metros/{id} endpoint returns information for the specified Metro.

curl -X GET -H 'X-Auth-Token: <API_TOKEN>' https://api.equinix.com/metal/v1/locations/metros/{id}

For example, using the ID of the New York metro, 932eecda-6808-44b9-a3be-3abef49796ef:

{
"id": "932eecda-6808-44b9-a3be-3abef49796ef",
"name": "New York",
"code": "ny",
"country": "US"
}