asn.dev

Internet exchange

FD-IX - St. Louis

active St. Louis, United States

Recorded members 31 addresses on file
Connected ports 15 across all participants
Peak traffic Not reported no figure on file
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
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/24IPv4Active15
2001:504:45:10::/64IPv6Active14

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

31 shown

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. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS6939Hurricane Electric LLC206.71.10.5Open
AS6939Hurricane Electric LLC2001:504:45:10::5Open
AS13335Cloudflare, Inc.206.71.10.6Open
AS13335Cloudflare, Inc.2001:504:45:10::6Open
AS20115Charter Communications LLC2001:504:45:10::11Selective
AS20115Charter Communications LLC206.71.10.11Selective
AS42WoodyNet, Inc.206.71.10.14Open
AS42WoodyNet, Inc.2001:504:45:10::14Open
AS29838Atlantic Metro Communications II, Inc.206.71.10.40Open
AS29838Atlantic Metro Communications II, Inc.2001:504:45:10::40Open
AS6325Illinois Century Network206.71.10.9Open
AS6325Illinois Century Network2001:504:45:10::9Open
AS3856Packet Clearing House, Inc.2001:504:45:10::13Open
AS3856Packet Clearing House, Inc.206.71.10.13Open
AS40948Stratus Networks2001:504:45:10::19Open
AS40948Stratus Networks206.71.10.19Open
AS14333On-Ramp Indiana, Inc. (ORI.NET)206.71.10.23Open
AS14333On-Ramp Indiana, Inc. (ORI.NET)2001:504:45:10::23Open
AS40181Elite Systems, LLC2001:504:45:10::12Open
AS40181Elite Systems, LLC206.71.10.12Open
AS54037DCA LLC206.71.10.21Selective
AS36243BPS Networks206.71.10.18Open
AS36243BPS Networks2001:504:45:10::18Open
AS400734Link Technologies, Inc.206.71.10.17Open
AS400734Link Technologies, Inc.2001:504:45:10::17Open
AS62948Air Link Rural Broadband, LLC206.71.10.20Open
AS62948Air Link Rural Broadband, LLC2001:504:45:10::20Open
AS13681MIDWEST INET EXCH LLC2001:504:45:10::252Open
AS13681MIDWEST INET EXCH LLC206.71.10.252Open
AS13681MIDWEST INET EXCH LLC2001:504:45:10::2Open
AS13681MIDWEST INET EXCH LLC206.71.10.2Open

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-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 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.