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.
A map of all Equinix data center locations is available at https://www.equinix.com/data-centers.
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 facility 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.
For the ways you can check inventory and monitor capacity, see the Inventory and Capacity page.
Metro-level Networking¶
The facilities 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 facilities 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 - While the blocks of private IPv4 addresses are facility-based, all the servers within a project in the same Metro can use them to connect to each other. If you need to set up connections between servers in different Metros, you can use Backend Transfer.
Metros Quick Reference¶
Americas¶
Region | Country | Metro | Code | Facilities |
---|---|---|---|---|
AMER | Brazil | Sao Paulo | SP | sp4 |
AMER | Canada | Montreal | MT | mt1 |
AMER | Canada | Toronto | TR | tr2 |
AMER | United States | Atlanta | AT | at4 |
AMER | United States | Chicago | CH | ch3 |
AMER | United States | Dallas | DA | da11, da6 |
AMER | United States | Los Angeles | LA | la4 |
AMER | United States | New York | NY | ny5, ny6, ny7 |
AMER | United States | Seattle | SE | se4 |
AMER | United States | Silicon Valley | SV | sv15, sv16 |
AMER | United States | Washington DC | DC | dc10, dc13 |
Europe and Middle-East¶
Region | Country | Metro | Code | Facilities |
---|---|---|---|---|
EMEA | Finland | Helsinki | HE | he7 |
EMEA | France | Paris | PA | pa4 |
EMEA | Germany | Frankfurt | FR | fr2, fr8 |
EMEA | Netherlands | Amsterdam | AM | am6 |
EMEA | Spain | Madrid | MD | md2 |
EMEA | Sweden | Stockholm | SK | sk2 |
EMEA | United Kingdom | London | LD | ld7 |
Asia-Pacific¶
Region | Country | Metro | Code | Facilities |
---|---|---|---|---|
APAC | Australia | Melbourne | ME | me2 |
APAC | Australia | Sydney | SY | sy4, sy5 |
APAC | Hong Kong | Hong Kong | HK | hk2 |
APAC | Japan | Osaka | OS | os3 |
APAC | Japan | Tokyo | TY | ty11 |
APAC | Korea | Seoul | SL | sl1 |
APAC | Singapore | Singapore | SG | sg1, sg4, sg5 |
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 |
|.... |.... |.... |
+--------------------------------------+----------------+------+
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"
}