Interconnection

AS37662 WIOCC-AS

Unclassified AFRINIC NSP

Exchanges 11 11 active

Countries 8 most in South Africa

Regions 2

Largest fabric 932 LINX LON1

Recorded presence

Internet exchanges

recorded

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

Exchange	Location	Their address	Policy	Member ports
LINX LON1	London, United Kingdom	195.66.226.85	Selective	932
Neutral Internet Exchange	Amsterdam, Netherlands	193.239.118.40	Selective	669
NAPAfrica IX Johannesburg	Johannesburg, South Africa	196.60.8.232	Selective	603
NAPAfrica IX Cape Town	Cape Town, South Africa	196.60.70.232	Selective	311
Kenya Internet Exchange Point - Nairobi	Nairobi, Kenya	196.223.21.100	Selective	155
NAPAfrica IX Durban	Durban, South Africa	196.10.141.232	Selective	146
Internet Exchange Point of Nigeria - Lagos	Lagos, Nigeria	196.216.148.87	Open	138
France-IX Marseille	Marseille, France	37.49.232.22	Selective	129
DE-CIX Marseille	Marseille, France	2001:7f8:36::931e:0:1	—	113
Ghana Internet Exchange Association	Accra, Ghana	196.201.2.127	Selective	27
AMS-IX Djibouti	Djibouti City, Djibouti	196.223.38.208	Selective	22

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.