Peer1IX
Internet Exchange
Services

Interconnection

Internet ExchangeMicro PoPsEdge Data Centers

Network Services

Data Center to Data CenterVirtual Connectivity HubData Center to CloudCloud to CloudPeer1ix Cloud RouterPeer1ix Virtual EdgeNAT GatewayPeer1ix PortVirtual Cross Connect

Security Services

DDoS ProtectionPeer1ix FWaaSIPsec Tunnel

Cloud Interconnect

Cloudflare Network Interconnect
Locations
Network toolsAll-in-One Network ReportBGP Looking GlassRPKI ValidatorBGP Security & Hijack CheckIP WHOISAS WHOISBGP Route ExplorerASN InsightsBGP Hijacks & Route LeaksInternet Outage TrackerCountry Internet InsightsTop Domains RankingDNS LookupSubnet CalculatorWhat Is My IP
BlogAboutContact Get connected

Private Peering With Virtual Cross Connects

· 1 min read · Peer1IX Team

Private Peering With Virtual Cross Connects

When traffic with one partner outgrows the public exchange, a virtual cross connect is the fastest way to set up private peering.

Outgrowing public peering

Public peering on the exchange LAN is efficient for many relationships. When traffic with one partner becomes very large, both sides often want a dedicated path for capacity planning and isolation.

A VXC as private peering

A Virtual Cross Connect between your port and your partner’s port creates that dedicated path without installing new hardware. You configure a BGP session over the VXC exactly as you would over a physical PNI.

Benefits

  • Separate capacity planning for the partner.
  • Traffic isolated from the shared peering LAN.
  • Clear visibility of volume to that partner.

Practical setup

  1. Agree bandwidth and VLAN with your partner.
  2. Order the VXC.
  3. Configure addresses and BGP over the new VLAN.
  4. Prefer the private session over public peering for that partner.

When to go physical

If the relationship grows to fill a large share of your port, consider a dedicated physical interconnect.

private peeringPNIVXC