Six markets
Kansas City, St. Louis, Houston, Springfield, Des Moines and Sioux City. KCIX also reaches Minneapolis and Southfield, MI.
IX.NET operates six exchanges across Missouri, Kansas, Iowa and Texas, and provides local access to five more in Seattle, Minneapolis, Denver, Dallas and New York.
One team, one application process and one set of policies, whether you need a single exchange or all eleven. The people running IX.NET have run KCIX since 2006.
Kansas City, St. Louis, Houston, Springfield, Des Moines and Sioux City. KCIX also reaches Minneapolis and Southfield, MI.
No monthly port fee on any IX.NET exchange, at any speed. You pay the data center for the cross-connect.
SIX, MICE, IX-Denver, DE-CIX Dallas and DE-CIX New York, handed off locally in Kansas City.
IX.NET doesn’t sell transit or colocation. Every member gets the same route servers and policies.
Each exchange has its own peering LAN, route servers and member list. Connect to one or all six. You pay the facility for the cross-connect.
How we keep ports freeSix buildings across the Kansas City metro, including Netrality KC2 in Shawnee, the first exchange in Kansas. Also reaches St. Louis, Houston, Des Moines, Minneapolis and Southfield, MI.
St. Louis, Peoria and Kansas City.
Three Houston buildings, plus Kansas City.
Springfield, plus Kansas City.
Des Moines, plus Kansas City.
Sioux City, plus Kansas City.
Get a port on a remote exchange’s peering LAN, handed off in Kansas City. Every extension has its own transport and port fee.
Content, cloud, Asia and western Canada. The largest US exchange by networks.
Upper Midwest ISPs and research networks at the Midwest Internet Cooperative Exchange.
A member-governed exchange for the Rocky Mountain region.
Where networks from Mexico and Latin America meet US networks.
Networks from Europe and the East Coast.
Network counts: PeeringDB, September 2026. MICE ports are billed yearly. MICE and IX-Denver cost the same as a direct port. Email us for current extension pricing.
peering@ix.netEvery location gets the same ports and route servers. All eleven exchange fabrics are available at 1530 Swift in Kansas City.
Extension ports for SIX, MICE, IX-Denver and DE-CIX are handed off in Kansas City. Ask about reaching them from your location.
An exchange is a shared switch in a data center. Networks connect once, then trade traffic directly with each other.
Traffic between two networks goes straight across the exchange, instead of through a third-party transit provider in another city.
Shorter paths mean faster connections. Traffic you exchange here no longer counts against your transit bill.
Any network with its own ASN: ISPs, hosting and content providers, cloud platforms, universities and enterprises.
Ports on our six exchanges are free. You pay for the cross-connect. Extension ports carry a port fee.
The process is the same at every exchange. Ask for several at once and we’ll set them up together.
Make sure your network’s PeeringDB record is current and lists your IRR AS-SET. The route servers filter on it.
Request your port: choose the exchange, then the building and speed. For an extension port, email peering@ix.net.
We send a letter of authorization. Order the cross-connect from the building; the facility may charge for it.
Bring up sessions with the route servers, peer bilaterally with anyone you like, and join the members’ mailing list.
Questions about peering or extension ports? Talk to our team.
Request a portAll fabrics use a 1500-byte MTU. Max-prefix recommendations are in each exchange’s PeeringDB notes.
| Exchange | IPv4 peering LAN | IPv6 peering LAN | Route servers | NOC |
|---|---|---|---|---|
| KCIX | 206.51.7.0/24 | 2001:504:1b:1::/64 | AS40542 | noc@kcix.net |
| STLIX | 206.83.12.0/24 | 2001:504:98::/64 | AS46389 | noc@stlix.net |
| HOUIX | 206.83.136.0/24 | 2001:504:9e::/64 | AS35920 | noc@houix.net |
| SpringIX | 149.112.4.0/24 | 2001:504:100::/64 | AS63203 | info@springix.net |
| DesMoinesIX | 149.112.17.0/24 | 2001:504:110::/64 | See site | info@desmoinesix.net |
| SIOUIX | 149.112.41.0/24 | See site | See site | noc@siouix.net |
Route-server communities: 0:peer-as keeps your routes from one peer; rs-as:peer-as sends them only to that peer; 0:rs-as keeps them from everyone. Read the peering policy.