asn.dev

Internet exchange

Milwaukee Internet Exchange

active Milwaukee, United States MKE

Recorded members 21 addresses on file
Connected ports 7 across all participants
Peak traffic 2.8 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
Milwaukee, United States
Region
North America
Airport code
MKE
Status
Active
PCH record updated
2020-05-21

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
204.107.122.0/24IPv4Active7
2602:f616::/64IPv6Active6

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

14 networks · 21 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 21 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS42WoodyNet, Inc.204.107.122.192602:f616::19as42-pch.mkeix.net—Open
AS26554US Signal Company, L.L.C.204.107.122.63——
AS3856Packet Clearing House, Inc.204.107.122.202602:f616::20as3856-pch.mkeix.net—Open
AS2381WiscNet204.107.122.44——
AS53597Hoyos Consulting LLC204.107.122.16204.107.122.1382602:f616::138—as53597-hoyosconsulting.mkeix.net—Open
AS32621Twin City VoIP, Inc.204.107.122.422602:f616::42as32621-mnvoip.mkeix.net—Open
AS3128University of Wisconsin System204.107.122.452602:f616::45——Open
AS4150SupraNet Communications, Inc.204.107.122.13——
AS168425Nines Data, LLC204.107.122.11——
AS397326South Front Networks204.107.122.1422602:f616::142——Open
AS30162Ethoplex, LLC204.107.122.14—Open
AS18719TSR Solutions, Inc.204.107.122.61as18719-tsrsolutions.mkeix.netOpen
AS26785Netwurx LLC204.107.122.12—Open
AS30216unnamed204.107.122.64——

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-13 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,177 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.