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.
  • A Peering subnet for Static and BGP routing, which is automatically assigned for the EIA service at no additional cost.

For these subnets, you can use:

Equinix-assigned IP Addresses​

Equinix-owned IPv4 and IPv6 addresses can be used with the Internet Access service. The minimum subnet size depends on the selected routing configuration.

Additional IP Address Space​

Before ordering, determine whether additional IP address space is required beyond the minimum for the intended use case or routing configuration. The following subnet sizes are available:

  • IPv4 subnets – /30, /29, /28, /27, /26, /25, /24 (except for Dual Direct VRRP configurations, where the smallest subnet possible is /29)
  • IPv6 subnets – /64, /48

Equinix-assigned IP addresses are non-portable and cannot be announced through other providers unless connectivity is available to the Equinix-aggregated announcement. The address space cannot be retained after leaving the Equinix Internet Access transit platform.

Important

Additional IPs must be requested at the time of order. Requests submitted after the order has been placed require a new order. Contact an Equinix representative for any regional differences. When the service is discontinued, the IP addresses are returned to the Equinix-owned address pool.

Customer-assigned IP Addresses​

Customer-assigned IP addresses allow the use of customer‑owned, publicly routable IP address space for use with Equinix Internet Access.

When using customer‑assigned IP addresses, the IP prefix must be properly registered in the Internet Routing Registry (IRR) and Resource Public Key Infrastructure (RPKI) systems so that Equinix (ASN 15830) can accept and globally propagate the route announcements.

Internet Routing Registry (IRR) Requirements​

Exact‑match route objects must be created for every prefix that will be announced. For example, announcing 198.51.100.0/24 requires a route object for 198.51.100.0/24 exactly, not only a covering prefix.

Route objects must be created in the IRR associated with the Regional Internet Registry (RIR), such as:

IP address space obtained from third parties may also be announced, provided the announcing organization is the legitimate holder of the address space.

RPKI Requirements (ROAs for ASN 15830)​

Resource Public Key Infrastructure (RPKI) enables IP prefixes to be cryptographically validated by networks worldwide.

To allow Equinix to announce a prefix, a Route Origin Authorization (ROA) must be created that authorizes ASN 15830 with the following parameters:

  • Origin ASN: 15830 (Equinix)
  • Prefix: The exact prefix to be announced (for example, 198.51.100.0/24)
  • Prefix lengths that exactly match the intended announcement (for example, a /24 announcement requires maxLength = 24)

ROAs must be created through the Regional Internet Registry (RIR) where the prefix is registered. Equinix cannot create or manage RPKI ROAs for customer subnets.

Prefix Size Requirements​

Equinix Internet Access requires the following minimum prefix sizes:

  • IPv4: /24
  • IPv6: /48

IRR objects and ROAs should match the intended announcements and meet the minimum size requirements.

ASN Requirements and Local‑AS Support​

Dedicated Internet Access ports support routing with a public Autonomous System Number (ASN).

EIA delivered via Fabric Port, Network Edge, or standard physical ports currently require the use of a private ASN provided by Equinix for BGP peering.

To retain a public ASN in these scenarios, the BGP Local‑AS feature may be used, subject to support by the network equipment vendor. This allows the public ASN to be maintained internally while satisfying the private ASN requirement for peering with Equinix.

Refer to router vendor documentation or contact an Equinix account team for guidance on configuring and using Local‑AS.

Propagation Time Before Service Activation​

After creating the required IRR route objects and RPKI ROAs, you must wait for global propagation. Allow up to 36 hours before creating or activating an Internet Access service. This ensures that Equinix systems can validate the prefixes and accept the route announcements.

Mixed IP Addresses​

Internet Access supports using both Equinix-owned IP addresses and BYOIP on the same service.

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 are not available on Internet Access over Dedicated Ports.

Was this page helpful?