Connect
About IX.NET

Neutral exchanges,
run by the same team
since 2006.

IX.NET operates KCIX, STLIX, HOUIX, SpringIX, DesMoinesIX and SIOUIX, and extends SIX, MICE, IX-Denver, DE-CIX Dallas and DE-CIX New York into Kansas City.

History

KCIX opened in Kansas City in 2006. Local networks started it to keep regional traffic in the region, instead of sending it to Chicago or Dallas and back. Its members and supporters have kept it free to join ever since, and it has grown into one of the largest exchanges in the United States by membership.

The same team went on to open STLIX in St. Louis, HOUIX in Houston, SpringIX in Springfield, DesMoinesIX in Des Moines and SIOUIX in Sioux City, all linked back to Kansas City. KCIX also opened the first exchange in Kansas, at Netrality KC2 in Shawnee.

The team also runs extension switches that bring five exchanges in other cities into Kansas City. IX.NET is the name for all of it: six exchanges it operates, five it extends, and the same way of working at each.

Neutrality

Neutral means IX.NET doesn't take sides between the networks that use it.

  • IX.NET doesn't sell transit or colocation, so it never competes with its members for their customers.
  • Every member gets the same ports, route servers and policies. No member pays for better treatment.
  • Networks connect in whichever building suits them. IX.NET doesn't steer members toward any data center or carrier.
  • Prices are the same for everyone and are published or available on request.

How we operate

  • Free ports on IX.NET exchanges. Supporters contribute hardware, services and labor, which keeps port fees at zero. Members pay only the data center for the cross-connect.
  • Extension port fees. Each extension has its own transport to the remote exchange, and its port fee covers that. MICE and IX-Denver ports cost the same as connecting to those exchanges directly.
  • Open peering. Route servers let a new member reach most of the exchange with one BGP session. Bilateral peering is always available too.
  • Public data. Participant lists, peering LANs and traffic statistics for each exchange are published on its site and in PeeringDB.
  • Best-effort service. Like most community exchanges, IX.NET exchanges are run on a best-effort basis, without a formal SLA.

Governance

IX.NET is independently operated. It isn't owned by a data center, carrier or content network.

Each exchange has a members' mailing list. Changes that affect members, such as new policies, pricing and planned maintenance, are announced there before they take effect. To join a list, email peering@ix.net.

Peering policy

Any network can join an IX.NET exchange if it meets these requirements.

  • Your own public ASN and IP address space.
  • A current PeeringDB record that lists your IRR AS-SET. The route servers build their filters from it, and some members automate peering from PeeringDB data.
  • Announce only prefixes you or your customers are entitled to announce, registered in an IRR.
  • Keep your technical contact details current, and respond to NOC contacts about your port.

Route server peering is optional. Route server communities let you control who receives your routes: 0:peer-as keeps your routes from one peer, rs-as:peer-as sends them only to that peer, and 0:rs-as keeps them from everyone. Max-prefix recommendations for each exchange are in its PeeringDB notes.

Port rules

These keep the shared peering LAN stable for everyone. A port that breaks them may be shut down until the problem is fixed.

  • One MAC address per port. All fabrics use a 1500-byte MTU.
  • Only IPv4, IPv6 and ARP frames. No spanning tree, CDP, LLDP, DHCP, router advertisements or other link-local protocols.
  • No broadcast or multicast traffic except ARP and IPv6 neighbor discovery.
  • Use only the IP addresses assigned to you on the peering LAN.
  • Don't send traffic to a member without their agreement, and don't point a default route at another member.

Accessibility

This site should work for everyone, including people who use a screen reader, a keyboard instead of a mouse, or zoomed text. It aims to meet WCAG 2.1 Level AA. If anything on it is hard to use, email peering@ix.net and we'll fix it, or get you the information another way.

Contact

Peering requests and questions: peering@ix.net. Operational issues: noc@ix.net.