asn.dev

Interconnection

AS3741 IS

Unclassified APNIC

Exchanges 10 10 active
Countries 5 most in South Africa
Regions 3
Largest fabric 1,077 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

Africa 7 Europe 2 Asia-Pacific 1

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.195.177Selective1,077
LINX LON1London, United Kingdom195.66.224.198Selective930
NAPAfrica IX JohannesburgJohannesburg, South Africa196.60.8.126Selective603
NAPAfrica IX Cape TownCape Town, South Africa196.60.70.126Selective311
Hong Kong Internet ExchangeHong Kong, China123.255.91.234Selective307
Johannesburg Internet ExchangeJohannesburg, South Africa196.60.96.10Selective218
NAPAfrica IX DurbanDurban, South Africa196.10.141.65Selective146
Cape Town Internet ExchangeCape Town, South Africa196.223.22.10Selective127
Durban Internet eXchangeDurban, South Africa196.223.30.10Selective104
TIX Tanzania - Dar es SalaamDar es Salaam, Tanzania196.223.5.71—32

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