Skip to main content
> Equinix Deploy

Peering Policy

Packet offers bare metal services with a variety of configurations and variety of datacenters around the world. Packet was acquired by Equinix in March 2020. To help make our vision for global, interconnected bare metal a reality, we've rebranded Packet as Equinix Metal™ and introduced new locations and features.

Peering Requests

Any external party that intends to peer with Equinix Metal AS54825 must have an up-to-date and fully completed entry with PeeringDB.

All peering requests should come via email to metal-peering@equinix.com. Equinix Metal will, in its sole discretion, assess peering requests and existing arrangements on a case-by-case basis considering the external party’s adherence to the best practices below and other factors.

Equinix Metal endeavors to respond, either inclined or declined, to all peering requests on a timely basis; however, take into account that Equinix Metal may not respond to provide reasons as to why any individual peering request is declined.

Peering Policy

In order to offer more connectivity quality and performance, Equinix Metal operates an international network (AS54825) and welcomes the opportunity to engage in peering with responsible BGP speakers that meet our minimum requirements and are present at mutual Internet Exchanges or data center facilities.

  1. Equinix Metal operates a selective peering policy which is generally open.
  2. Peers must operate a public and visible ASN.
  3. Where multiple connections to an IX exist, peers must establish BGP sessions with all neighbors and enable multipath routing.
  4. Equinix Metal has not established a minimum bandwidth threshold for establishing peering.
  5. Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purpose of filtering. Both parties shall make good faith efforts to keep this information up to date.
  6. Either party may accept or reject peering requests as network management needs require.
  7. Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP.
  8. Neither party shall announce to the other the more specific routes of prefixes learned via a third-party transit customer.
  9. Both parties will exchange only Unicast IPv4/6 routes.
  10. Both parties must maintain an up to date PeeringDB entry, including a 24x7 NOC Contact.
  11. Equinix Metal does not require use of an MD5 key for protecting BGPv4 sessions, but we can do it if requested.
  12. Equinix Metal requires the other party to register their routes in the RPKI repository using Route Object Authorization (ROA) objects.
  13. Peers are encouraged to implement Mutually Agreed Norms for Routing Security (MANRS).

Meeting the criteria specified here does not guarantee that Equinix Metal will establish a peering relationship with the applicant.

Peering Information

Contact Information

Copied code to clipboard