IP Address Allocation

Depending on your routing configuration, your Internet Access service needs the following subnets.

• Static, Direct, and BGP routing all require a LAN subnet.

  Your LAN subnets can be:

  • Equinix-owned IP Addresses - Lease provider-assigned IP Blocks owned by Equinix.
  • Customer-owned IP Addresses - Onboard provider-independent IP Blocks that you own or are authorized to use.
  • Mixed IP Addresses - Use both your own and Equinix-owned public IP addresses.

• If you are using Static or BGP routing, you also need a Peering subnet.

  Peering subnets use Equinix-owned IP Addresses and are automatically assigned when you create the service at no additional cost. Peering subnets do not support customer-owned IP addresses.

Equinix-owned IP Addresses

Equinix-owned IPv4 and IPv6 address blocks can be used with the Internet Access service.

When you order internet access, you select a subnet of Equinix-owned IP addresses from your IP Blocks inventory to use for your LAN subnet. You can also order a new Equinix-owned IP Block.

The following subnet sizes are available:

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

If you are using Static or BGP routing, your service is automatically assigned a peering subnet of Equinix-owned IP addresses. The minimum subnet size depends on the selected routing configuration.

Customer-owned IP Addresses

Equinix Internet Access supports the use of customer-owned or authorized, publicly routable IP address space.

When using customer-owned IP addresses, a Route Object (RO) must be created in the Internet Routing Registry (IRR) associated with the Regional Internet Registry (RIR), or another IRR such as the Routing Assets Database (RADb). Equinix recommends using a Regional Internet Registry’s IRR.

If you’re using a public ASN the Route Object must match the public ASN your public prefix. If you’re using a private ASN the Route Object must match Equinix’s public ASN (15830) and your prefix. The Route Object is required for the internet access service to accept a prefix received from you, or used on a Direct service, and advertise that prefix to upstream peers and providers.

Equinix recommends, but does not require, that you create a Resource Public Key Infrastructure (RPKI) Route Origin Authorization (ROA) for your prefix and relevant ASN as well. When creating an ROA, it is important to make sure it’s properly configured. An invalid ROA will cause the matching prefix to be dropped by the service.

For more information on Route Objects and RPKI topics, see the IP Blocks Overview.

To use a customer-owned IP Block with Internet Access, onboard it into your IP Blocks either before or during ordering.

Prefix Size Requirements

Equinix Internet Access requires the following minimum prefix sizes:

• IPv4: /24
• IPv6: /48

Internet Routing Registry Route Objects should match the intended announcements and meet the minimum size requirements. RPKI Route Origin Authorizations, if they exist, must match the intended announcements and meet the minimum size requirements.

Propagation Time Before Service Activation

After creating the required IRR route objects (ROs), 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.

ASN Requirements and Local‑AS Support

Dedicated Internet Access ports support routing with customer public Autonomous System Numbers (ASNs).

Internet Access services delivered via Fabric Port or to Network Edge currently require the use of a private ASN provided by Equinix for BGP peering.

To retain the use of a public ASN, for the routing process or as an origin 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 the router vendor documentation or contact an Equinix account team for guidance on configuring and using Local‑AS.

Mixed IP Addresses

Internet Access supports using both Equinix-owned and customer-owned IP addresses on the same service. Mixed IP addresses are supported for the following routing configurations:

Configuration	Internet Access Over Fabric	Internet Access to Network Edge
Single Static Routing	Supported	Supported
Dual Static VRRP	Supported	NOT Supported
Single Direct Routing	NOT Supported	NOT Supported
Dual Direct VRRP	NOT Supported	NOT Supported
Single BGP	Supported	Supported
Dual BGP	Supported	Supported

Mixed IP addresses are not available on Internet Access over Dedicated Ports.