asn.dev

Internet exchange

MidWest-IX - St. Louis

active St. Louis, United States STL

Recorded members 39 addresses on file
Connected ports 18 across all participants
Peak traffic 5.3 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
St. Louis, United States
Region
North America
Airport code
STL
Status
Active

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
206.71.10.0/24IPv4Active18
2001:504:45:10::/64IPv6Active17

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

18 networks · 39 addresses

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. Each network's addresses on the fabric are listed together, IPv4 first. Typing in the box narrows the rows below; Search looks through all 39 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS6939Hurricane Electric LLC206.71.10.52001:504:45:10::5——Open
AS13335Cloudflare, Inc.206.71.10.62001:504:45:10::6——Open
AS29838Atlantic Metro Communications II, Inc.206.71.10.402001:504:45:10::40——Open
AS42WoodyNet, Inc.206.71.10.142001:504:45:10::14——Open
AS63293Facebook, Inc.206.71.10.162001:504:45:10::16——Selective
AS6325Illinois Century Network206.71.10.92001:504:45:10::9——Open
AS3856Packet Clearing House, Inc.206.71.10.132001:504:45:10::13——Open
AS19754The Fusion Network, LLC206.71.10.262001:504:45:10::26——Open
AS40948Stratus Networks206.71.10.192001:504:45:10::19——Open
AS14333On-Ramp Indiana, Inc. (ORI.NET)206.71.10.232001:504:45:10::23——Selective
AS36243BPS Networks206.71.10.182001:504:45:10::18——Open
AS40181Elite Systems, LLC206.71.10.122001:504:45:10::12——Open
AS54037DCA LLC206.71.10.21—Selective
AS400734Link Technologies, Inc.206.71.10.172001:504:45:10::17——Open
AS62948Air Link Rural Broadband, LLC206.71.10.202001:504:45:10::20——Open
AS13681MIDWEST INET EXCH LLC206.71.10.3206.71.10.252206.71.10.22001:504:45:10::2522001:504:45:10::22001:504:45:10::3——————Open
AS212232Port 179 LTD206.71.10.42001:504:45:10::4——Open
AS395886KURUN CLOUD INC.206.71.10.112001:504:45:10::11——Selective

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-10-15 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 97,714 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.