Two ways to exchange traffic directly
Both public and private peering let two networks exchange traffic without paying a transit provider. The difference is the medium.
Public peering happens over the exchange’s shared layer-2 fabric. You connect one port and can peer with any member on that LAN.
Private peering uses a link dedicated to two networks — traditionally a physical cross-connect (often called a private network interconnect, or PNI), or a private VLAN across an exchange fabric.
When public peering is the right choice
Public peering is ideal when you want to reach many networks with modest traffic to each. A single 10G port might carry traffic to dozens of peers, none of which individually justify a dedicated link. It is also the fastest way to start: once your port is up, every route-server participant is reachable.
When private peering makes sense
Once traffic with a single partner becomes large and predictable — for example between a big access ISP and a major content network — a dedicated link gives you guaranteed capacity, isolates that traffic from the shared port, and simplifies capacity planning for both sides.
Private VLANs: the middle path
Physical cross-connects take time and add recurring cost. On Peer1IX, you can create a private VLAN to a partner over the port you already have. You get a point-to-point path for that relationship, separate from the public peering LAN, without pulling new fibre. If traffic keeps growing, you can move to a dedicated port later.
A practical progression
- Join the exchange and peer publicly through the route servers.
- Watch your traffic graphs to find your largest partners.
- Set up bilateral sessions with them for more control.
- Move the heaviest relationships to private VLANs or dedicated ports.
The bottom line
It is rarely either-or. Public peering gives breadth; private peering gives depth. A neutral exchange that supports both on the same infrastructure lets you grow from one to the other without redesigning your edge.
