Skip to main content

IP Address Allocation

Depending on your routing configuration, you need the following subnets:

  • A LAN subnet for Static, Direct, and BGP routing. If you are using Direct routing, this is the only subnet you need.
  • A Peering subnet for Static and BGP routing.

For these subnets you can use:

Provider-Assigned IP Addresses​

You can use Equinix-owned IPv4 and IPv6 addresses for your Internet Access service. The minimum size of the subnet depends on your routing configuration.

ConfigurationIPv4 subnet sizeIPv6 subnet size
Single-Homed Direct/30/64
Single-Homed Static/30/64
Single-Homed BGP/30/64
Dual-Homed VRRP Direct/29/64
Dual-Homed VRRP Static/29/64
Dual-Homed BGP2 x /302 x /64

Provider-assigned (PA) IP addresses are non-portable and aren't announced through other providers unless connectivity is available to the Equinix-aggregated announcement. Initial Equinix assignments enable service interconnection between you and Equinix. You can't keep the address space after leaving the Equinix Internet Access transit platform.

Additional IP Address Space​

Determine if you need more IP address space above the minimum for your use-case or routing configuration before ordering. The following subnet sizes are available:

  • IPv4 subnets – /30,/29, /28, /27, /26, /25, /24
  • IPv6 subnets – /64, /48

These addresses can be purchased as IPv4 only, IPv6 only, or as a dual stack where IPv4 and IPv6 are combined.

Important

Additional IPs must be requested at the time of order. Requests for additional IPs after the order has been submitted require an new order.

Contact your Equinix representative for any regional differences. When you discontinue the services, these addresses are returned to the Equinix-owned pool of addresses.

Provider-Independent IP Addresses​

Using Provider-independent (PI) IP addresses allows you to bring your own publicly routable IP addresses to use for your Internet Access routing.

If you choose to bring your own IP addresses, you must create the appropriate route objects and Route Origin Authorization (ROA) in an Internet Routing Registries (IRR) database to announce your IP address space with Equinix's ASN 15830.

If you are using BGP routing, Internet Access allows you to announce your IP addresses using a private ASN, provided you create valid route objects and configure Resource Public Key Infrastructure (RPKI) ROAs with Equinix 15830 as the origin. Currently, use of a public ASN is only supported on Internet Access service on dedicated ports. Until full support for public ASN peering is available, customers deploying EIA with Fabric Port, Network Edge, or physical ports who want to maintain their public ASN may use the BGP Local-AS feature, if supported by their network vendor. This feature enables customers to retain their public ASN and meet the current requirement to use a private ASN for EIA peering. For more information on the use of this feature, please consult your vendor documentation or contact your Equinix account team.

Internet Access subnets require a minimum prefix size of /24 for IPv4 addresses or /48 for IPv6 addresses. To ensure global reachability, you must have one or more suitable route objects which exactly match their planned prefix announcements.

You can request IP address resources from these providers:

  • ARIN – American Registry for Internet Numbers, www.arin.net

  • RIPE – Réseaux IP Européens Network Coordination Centre, www.ripe.net

  • APNIC – Asia-Pacific Network Information Centre, www.apnic.net

  • LACNIC – Latin America and Caribbean Network Information Centre, www.lacnic.net

  • AFRINIC – African Network Information Center, www.afrinic.net

You can also request IP address resources from third-parties and announce any space you legitimately own.

After registering your subnet in an Internet Registry, you must wait 36 hours before attempting to create an Internet Access service. Approximately 36 hours are required to propagate information from a registry to Equinix.

Equinix cannot create RPKI ROAs for your subnets. These values must be created through the Regional or National Internet Registry where the prefix is currently registered.

Mixed IP Addresses​

Internet Access supports using both Equinix-owned IP addresses and BYOIP on the same service. For example, if you want to use your own IP addresses for the peering subnet, but lease Equinix-owned IP addresses for the LAN subnet.

Using Mixed IP addresses are supported for the following routing configurations:

ConfigurationInternet Access Over FabricInternet Access Over Network Edge
Single Static RoutingSupportedSupported
Dual Static VRRPSupportedNOT Supported
Single Direct RoutingNOT SupportedNOT Supported
Dual Direct VRRPNOT SupportedNOT Supported
Single BGPSupportedSupported
Dual BGPSupportedSupported

Mixed IP Addresses is not available on Internet Access over Dedicated Ports.