Connection guide

Connection process

1. Contact the exchange

   Send your organisation name, public ASN, preferred port speed and NOC contact details to peering@kent.exchange.

2. Confirm the port and location

   Agree the port option and connection details for Vinters Connect, Maidstone. Arrange transport and any required cross-connect with your provider.

3. Supply routing information

   Provide your IRR as-set and registry, PeeringDB entry, and expected IPv4 and IPv6 prefix counts. The exchange allocates peering addresses and confirms the route server configuration.

4. Configure and establish peering

   Configure the peering interface with the agreed addresses and MTU. Establish BGP sessions with both route servers, then confirm routing and reachability with the NOC.

Connection requirements

Membership is open to organisations with a public ASN. Connected interfaces must meet the following requirements.

• One MAC address per port. No bridging, VRRP, CARP or forwarding between members.
• IPv4 and IPv6 unicast only. No proxy ARP, DHCP, router advertisements, BPDUs, discovery protocols or IGPs.
• 1500-byte MTU. Use the same MTU on the peering interface.
• Announce only your own routing cone. Your prefixes and your customers’ prefixes must be covered by the registered IRR as-set.
• No default route through the fabric. The peering LAN does not provide transit or a default gateway.
• Maintain registry information. Keep your IRR objects current and publish ROAs with appropriate maximum prefix lengths.

Full route server filtering policy →

Peering enquiries

Email peering@kent.exchange with your connection request. For existing sessions and network incidents, contact noc@kent.exchange.