asn.dev

Interconnection

AS53597 HOYOS-CONSULTING-LLC

Unclassified ARIN NSP

Exchanges 10 10 active
Countries 1 most in United States
Regions 1
Largest fabric 350 Seattle Internet Exchange

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS53597, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's page, with its peering LANs and everyone else on it.

North America 10

ExchangeLocationTheir addressPolicyMember ports
Seattle Internet ExchangeSeattle, United States206.81.81.136Open350
Equinix Internet Exchange ChicagoChicago, United States208.115.136.60Open282
Fremont Cabal Internet ExchangeFremont, United States206.80.238.67—182
Midwest Internet Cooperative ExchangeMinneapolis, United States206.108.255.65Open154
Northwest Access ExchangePortland, United States198.32.195.93Open104
Interconnection eXchange DenverDenver, United States206.53.175.221Open93
Kansas City Internet ExchangeKansas City, United States206.51.7.110Open72
United IX ChicagoChicago, United States206.41.110.67Open69
Quad Cities Internet ExchangeDavenport, United States206.83.43.22Open67
Milwaukee Internet ExchangeMilwaukee, United States204.107.122.16—7

Recorded rather than inferred: an address on a peering LAN is at that exchange by definition. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. An absent exchange means PCH has no record of it, not that the network is not there. For the operator's own claims, see its PeeringDB record.

From the exchange directory collected 2026-10-11 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,138 recorded member ports, licensed CC BY-NC-SA 3.0.

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.