Offer a managed gateway service, native to Equinix Fabric, that supports hybrid, multi-cloud routing in all Fabric locations, delivered as a Layer 3 capable per customer Virtual Routing Function (VRF).

It would be great to have support for Bidirectional Forwarding Detection (BFD) in the Metal VRF feature for quicker failover. BFD support should also be added for traditional L3 BGP sessions on Metal.

Currently only dedicated fabric ports can participate EVP-LAN. Being service token based, Metal VCs are not able to participate EVP-LAN. It'd provide great benefits for Metal customers to enable metal fabric VCs to join EVP-LAN

Cloud-inspired load balancer service for distributing traffic to Metal servers and appliances. At launch, Equinix Metal's Load Balancers will support users deploying a fully managed L3/L4 network load balancing from the Metal portal interface. Load Balancers will initially support public traffic on the ingress virtual IP (VIP) and support public IP "real servers" access with direct server return. No private NAT or network traffic for real servers will be supported at launch.

Provide a VLAN to connect from one project to another within Metal over a VLAN dedicated to the purpose, to share a resource (such as Pure storage) with multiple projects.

LACP 802.3ad has two settings for periodic transmissions / LACPDU, fast and slow. Currently, the LACP pairing between Metal instance LACP and it's attached network (ToR) only allow for LACP slow. For certain use cases, LACP fast can enable more elegant / responsive failure behaviors for systems deployed above Metal instances. Being able to specify that an instance's LACP configuration from the switch side be "fast" would enable this functionality.

Enable customers - especially customers with certain security requirements - to bootstrap Virtual Devices without any pre-configured network interfaces or default services (such as Internet)

Formalize and expand existing DDoS (Distributed Denial of Service) protections on the Equinix Metal network to mitigate common attack methodologies including UDP, SYN, HTTP floods, etc. Enable ecosystem solutions (e.g. on Network Edge or via Fabric) for advanced use cases.

Currently it's not possible to bond all 4 network ports of the n2.xlarge.x86 / n3.xlarge.x86 / a3.large.x86 into a single LACP bond. It would be useful to have that as an option for high network throughput requirements. 4x port LACP should be available in both Layer 3 and Layer 2 modes.

Support Virtual Routing & Forwarding (VRF) to support private, overlapping Layer 3 connectivity leveraging a customer's own public or private IPv4 blocks.