IndyIX Logo

IndyIX Documentation

Policies & Technical Requirements

The following policies and technical requirements apply to all IndyIX members and participants. Please review these terms before connecting to the exchange.

General Requirements

  • Peering members must have a registered, public Autonomous System Number (ASN) issued by a Regional Internet Registry (RIPE, ARIN, APNIC, LACNIC, or AfriNIC).
  • Members must provide a Network Operations Center (NOC) contact during sign-up for operational communication and issue resolution.
  • Members must notify IndyIX of changes to NOC points of contact within a reasonable time frame.
  • Members must have a physical connection to the IndyIX peering fabric; tunnels are prohibited. However, remote connections via L2/Wavelengths/Dark Fiber are allowed within a reasonable geographic distance or from a neighboring metro.
  • IndyIX is not liable for losses or damages from interruptions or disruptions to the peering fabric, and the service is provided "as is" without warranties.
  • Each peering member is permitted to connect one network and one MAC address per port. Exceptions can be made if a peering member wishes to share their port with their customers, please contact us for approval.
  • Participants are limited to peering from one location only, regardless of the number of physical or logical ports.

Technical Requirements

  • Members may not point default routes or use another member's or IndyIX's resources without explicit permission.
  • BGPv4 must be used for routing, with the NEXT_HOP_SELF attribute set when advertising routes.
  • Only the following Ethertypes are permitted: IPv4 (Ethertype 0x0800), IPv6 (Ethertype 0x86DD), and ARP (Ethertype 0x0806).
  • Announced prefixes must be registered to the member and associated with the appropriate Internet Routing Registry (IRR). IndyIX Route Servers currently accept prefixes from the following IRR databases: AFRINIC, APNIC, ARIN, LACNIC, RADB, RIPE
  • Minimum prefix announcements are /24 for IPv4 and /48 for IPv6; members are encouraged to aggregate prefixes to reduce routing table size.
  • Non-unicast traffic is limited to broadcast ARP and multicast ICMPv6 Neighbor Discovery packets. Per-neighbor timeouts for such traffic should not exceed four (4) hours.
  • IndyIX prefixes must not be propagated externally and should be minimized in internal routing.