❀ Kawaii IX

Peering Policy

Kawaii IX operates an open peering policy. We welcome all networks that meet the requirements below.

Open Peering Policy

Kawaii IX welcomes all networks. There are no restrictive membership requirements.

Eligibility Requirements

To connect to Kawaii IX, a participant must:

  1. Operate a network with a publicly registered ASN from a Regional Internet Registry (RIR).
  2. Be registered on PeeringDB.
  3. Have a physical presence at Qupra DC, or arrange a cross-connect/remote peering connection.

Technical Requirements

All participants must comply with the following technical requirements:

  • Only unicast traffic is permitted on the peering LAN. No broadcast (except ARP/NDP), no multicast.
  • Proxy ARP must be disabled on the peering interface.
  • Only one MAC address per port is allowed.
  • The peering port must be configured as an access port (no 802.1q tagging) unless otherwise agreed.
  • Spanning Tree Protocol (STP) frames must not be sent to the peering LAN.
  • Recommended MTU: 9000 bytes (jumbo frames supported).

Route Server Usage

Use of Kawaii IX route servers is optional but encouraged. Route servers allow participants to establish peering with all connected networks through a single BGP session.

Route servers perform RPKI validation and IRR filtering to ensure only legitimate routes are distributed. See the Members page for route server details.

Prohibited Activities

The following activities are prohibited on the Kawaii IX peering LAN:

  • Pointing a default route at the exchange fabric or any other participant.
  • Sending traffic to IP addresses not explicitly advertised via BGP by the destination participant.
  • Any form of abuse, including DDoS attacks, port scanning, or unauthorized access attempts.