Skip to content

Standard IPs

When a Equinix Metal™ server is installed, we configure management IP addresses by default. These IPs are for accessing a server administratively, for example, via SSH. It is important to consider that these IPs live and die with a server -- when a server instance is deleted, its management IPs also cease to exist, and may not necessarily be assigned to any new servers created.

We also allow our customers to provision supplementary elastic IP addresses. These are special addresses which can move between servers in a project. Elastic IPs are recommended for any workload where permanent reachability is required, for example, hosting a public-facing web site behind a load balancer, or directing clients to a clustered database server internally.

Types of IP Addresses at Equinix Metal

IP addresses come in many colors, shapes, and sizes, and one size does not necessary fit all. One important distinction is "free" vs "paid". The following IP address assets are free:

  • Public IPv4 - These are public-facing Internet addresses. Unlike other cloud hosting providers, we provide raw, unfettered, access to the Internet, without any firewalling or Network Address Translation (NAT). Each new server is provisioned with a single public IPv4. This IP address cannot be retained after you delete a server.

  • Private IPv4 - These are internal (10.x.x.x) IP addresses, provided at no charge. A client project is pre-provisioned with a /25 by default; we’ll automatically replenish your supply with additional /25s as you spin up additional resources. Client servers are able to reach other private IPs belonging to their project, however clients are unable to communicate with other projects or Equinix Metal customers at these addresses.

  • Public IPv6 - We assign a (publicly routable) /56 on the project level, which is divisible into 256 /64s (“LAN subnets” in IPv6 parlance), each routable to a server. IPv6 addressing is also provided at no charge.

If you want retain your IP addresses and move them between servers (or facilities). In this case we have both "local" and "global" elastic IP addresses, which you rent from Equinix Metal on an hourly basis:

  • Elastic IPs - Clients can use our customer portal to order additional public IPv4 address space, ranging from a /32 (a single IP) through a /24 (256 IPs). Though there is no technical limit to how these IPs can be configured, we encourage you to use them responsibly, and as such we charge a nominal fee per elastic IP address ($0.005/hr or about $3.60/mo). Usage details below.

  • Global Anycast IPs - Global Anycast IPs are public IPv4 addresses that are pulled from Equinix Metal-owned IP space and announced in all of Equinix Metal's core facilities. These IPv4 addresses cost $0.15/hr per IP. Regular $0.05/GB outbound rates apply, and (in addition) inbound bandwidth to Global Elastic IPs costs $0.03/GB. Read more.

Creating a Reserved Subnet via Customer Portal

Select the Project in which the reserved subnet is required. From within that specific project, click on IPs & Networks & click on Request IP Addresses

From the slide out, you can select the size, type, and facility of the reserved subnet. Be sure to include detailed information for the use case for the requested subnet.

Equinix Metal allows you to reseve the following sizes:

Elastic IPs Usable Global Anycast Usable
/31 2 IPv4 /32 1 IPv4
/30 4 IPv4 /31 2 IPv4
/29 8 IPv4 /28 4 IPv4
/28 16 IPv4

projects-ips-networks

Provisioning a server with a single reserved subnet via Customer Portal

deploy-reserved-subnet

Provisioning a server with multiple reserved subnets via Customer Portal

deploy-reserved-subnets-multi

Creating an IP Reservation through the API

curl  -v \
      -X POST "https://api.packet.net/projects/$PROJECT_ID/ips" \
      -H 'Content-Type: application/json' \
      -H "X-Auth-Token: $PACKET_API_TOKEN" \
      -d @- <<-'EOF'
      {
        "type": "public_ipv4",
        "quantity": 4,
        "comments": "for mytestserver.com",
        "facility": "ams1",
        "details": "my /30 in AMS1"
      }
EOF

Please Note: The quantity parameter should be the number of IPs in the subnet, valid values are 2, 4, 8, 16. IP reservations larger than 16 will require additional verification by Equinix Metal)

The output would be similar to:

{
  "id":"18c40668-f9b6-4cdc-b50e-0f8729d4f2f6",
  "address_family":4,
  "netmask":"255.255.255.252",
  "created_at":"2020-02-20T18:53:52Z",
  "details":"my test /30 in AMS1",
  "tags":[],
  "public":true,
  "cidr":30,
  "management":false,
  "manageable":true,
  "enabled":true,
  "global_ip":false,
  "customdata":{},
  "addon":true,
  "bill":true,
  "project":{"href":"/projects/c895ea67-40ce-4f98-bd97-fe0b2e771481"},
  "project_lite":{"href":"/projects/c895ea67-40ce-4f98-bd97-fe0b2e771481"},
  "assignments":[],
  "facility":{"id":"8e6470b3-b75e-47d1-bb93-45b225750975","name":"Amsterdam, NL","code":"ams1","features":["baremetal","storage","global_ipv4","backend_transfer","layer_2"],"address":{"href":"#0688e909-647e-4b21-bdf2-fc056d993fc5"},"ip_ranges":["2604:1380:2000::/36","147.75.204.0/23","147.75.100.0/22","147.75.80.0/22","147.75.32.0/23"]},
  "network":"147.75.80.220",
  "address":"147.75.80.222",
  "gateway":"147.75.80.221",
  "available":"/ips/18c40668-f9b6-4cdc-b50e-0f8729d4f2f6/available",
  "href":"/ips/18c40668-f9b6-4cdc-b50e-0f8729d4f2f6"
}

Please Note: Should you not recieve a response from the above. A support ticket was submitted on your behalf, and our team will review the request an respond. Should you not see this ticket please email us directly

Deploy without Public IP

The servers provisioned on Equinix Metal gets allocated a public IPv4 and IPv6 address by default. However, there are scenarios where the server is deployed in a restricted environment and expected to have no public internet access. The “Deploy without public IP feature” does exactly that by provisioning a server without any public IP on it. This works for On-demand servers as well as reserved hardware and spot instances.

Should you attempt to use a non-supported operating system without a public IPv4 address, it will receive an error like “Public IPv4 is required ”.

In order to deploy without public IPv4 or public IPv6, uncheck those boxes and select the desired Private IPv4 subnet range. The Deploy without Public IPv4 feature is also supported through the API.