asn.dev

Interconnection

AS28458 IENTC S DE RL DE CV

Unclassified LACNIC

Exchanges 12 11 active
Countries 5 most in United States
Regions 3
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS28458, 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 6 Europe 4 Latin America 2

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.195.210Open1,078
LINX LON1London, United Kingdom195.66.228.58Open931
AMS-IX AmsterdamAmsterdam, Netherlands80.249.208.221Open882
Neutral Internet ExchangeAmsterdam, Netherlands193.239.119.246Open669
Coresite - Any2 WestLos Angeles, United States206.72.211.69Open344
Any2 CaliforniaLos Angeles, United States206.72.211.69Open319
Equinix Internet Exchange DallasDallas, United States206.223.119.50Open231
Equinix Internet Exchange MiamiMiami, United States198.32.243.221Open178
DE-CIX DallasDallas, United States206.53.202.147Open176
PIT MXQuerétaro, Mexico200.23.206.58Open49
NIX MonterreyMonterrey, Mexico45.68.68.16Open11
Equinix-LA(former Paix) retiredLos Angeles, United States198.32.243.221Open—

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