At Gig-IX we try to be as inclusive as possible which is reflected by our low or non-existent port fees, however, there are some technical and administrative rules which must be followed by all exchange participants. Failure to comply with these rules my result in your port being disabled, or for repeated offenses your membership may be terminated.
- Networks are only allowed to connect to Gig-IX using a public ASN allocated by an RIR (ARIN, RIPE, etc). Private ASNs and reserved ASNs are not permitted on the exchange.
- Networks must only announce IP space which your network owns or has explicate permission to announce.
- An updated IRRDB AS-SET is absolutely essential to peer over the IX - Gig-IX's route servers implement strict IRR filtering at all PoPs.
- Participants must indicate if they will participate in peering with the route server, if a member indicates they will peer with the route server then they must actually configure the peering session.
- Network operators must maintain up to date contact details on PeeringDB. Operators are also encouraged to update their PeeringDB profiles to reflect any Gig-IX PoP they peer at.
- Pointing static or default routes to any other member without their explicate permission is strictly prohibited.
- The only protocols allowed on the peering VLAN are ARP, IP, IPv6 and IPv6 ND. All other protocols (such as LLDP, CDP, etc) must be disabled.
- Gig-IX does not currently accept remote peering (via GRE, L2TP, etc). Participants must have a physical presence in one of our datacenters to get connected. Peering via VPS is supported.