bgpreport

Exchanges · data from 2026-11-12

MKE-IX The Milwaukee Internet Exchange

Milwaukee, US · members from IX Report (2026-11-12)

9Members 9 originate routes
480Their routes 93.3% RPKI valid · 92.7% with a route object
0RPKI invalid from 0 members
32No ROA 35 with no route object for their origin
6AS-SET includes own ASN 0 missing it · 0 not found · 3 none
1Route-server members 0 of their 2 routes left out by an RPKI + IRR filter

Route servers: RPKI + IRR filtering

For each member on the route servers: of the routes it originates, how many a route server would leave out if it dropped RPKI-invalid routes and filtered on the IRR the way IXP route servers commonly build their prefix lists: the member's AS-SETs from PeeringDB (with none, its own AS number), expanded as bgpq4 does against whois.radb.net, with more-specifics of a route object accepted down to /24 and /48 (bgpq4 -A -R 24 / -R 48). 0 routes are RPKI invalid and 0 fail the IRR filter. Only each member's own routes are counted: the collectors show a route's origin, not which network it came through, so customers' routes aren't in these numbers. Route objects only in LEVEL3 or IDNIC (no public dump) count as missing.

Every route the route-server members originate would be accepted.

Members

Every member on IX Report's lists for MKE-IX, with the routes it originates. Also as members.csv.

AS42PCH AS42 No 418210 v4 · 208 v6 99% 0 95% includes own ASN
AS3128University of Wisconsin System No 1312 v4 · 1 v6 100% 0 92% includes own ASN
AS53597Hoyos Consulting No 137 v4 · 6 v6 92% 0 85% includes own ASN
AS394621Data Holdings No 1110 v4 · 1 v6 18% 0 55% none in PeeringDB
AS32621Minnesota VoIP No 87 v4 · 1 v6 12% 0 88% includes own ASN
AS26785Netwurx No 76 v4 · 1 v6 0% 0 71% none in PeeringDB
AS18719TSR Solutions No 55 v4 · 0 v6 0% 0 60% none in PeeringDB
AS397326South Front Networks No 32 v4 · 1 v6 100% 0 100% includes own ASN
AS3856PCH AS3856 Yes 21 v4 · 1 v6 100% 0 100% includes own ASN