asn.dev

Interconnection

AS25192 CZNIC-AS

Unclassified RIPE

Exchanges 11 11 active
Countries 9 most in Sweden
Regions 5
Largest fabric 2,704 IX.br (PTT.br) São Paulo

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS25192, 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.

Europe 6 North America 2 Africa 1 Asia-Pacific 1 Latin America 1

ExchangeLocationTheir addressPolicyMember ports
IX.br (PTT.br) São PauloSão Paulo, Brazil187.16.211.110—2,704
DE-CIX FrankfurtFrankfurt, Germany80.81.192.112Open1,078
Milan Internet ExchangeMilan, Italy217.29.67.72—418
Giganet Internet ExchangeKyiv, Ukraine185.1.63.124Open355
Seattle Internet ExchangeSeattle, United States206.81.80.138Open350
Singapore Internet ExchangeSingapore, Singapore103.16.102.189Open277
Johannesburg Internet ExchangeJohannesburg, South Africa196.60.97.18Open217
NIX.CZ - Neutral Internet eXchange for the Czech RepublicPrague, Czech Republic91.210.16.3Open208
Netnod StockholmStockholm, Sweden195.69.119.68—77
Equinix Los Angeles IBXLos Angeles, United States206.223.123.76—72
Netnod Sundsvall- GävleSundsvall, Sweden194.68.128.68Open18

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.