Interconnection

AS30999 EMTEL-AS-AP

Residential AFRINIC

Exchanges 11 11 active

Countries 7 most in South Africa

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 AS30999, 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 6 Europe 3 Asia-Pacific 2

Exchange	Location	Their address	Policy	Member ports
DE-CIX Frankfurt	Frankfurt, Germany	80.81.195.209	Open	1,078
Neutral Internet Exchange	Amsterdam, Netherlands	193.239.118.74	Open	669
NAPAfrica IX Johannesburg	Johannesburg, South Africa	196.60.10.53	Open	603
Equinix Internet Exchange Singapore	Singapore, Singapore	27.111.230.196	Open	496
Singapore Internet Exchange	Singapore, Singapore	103.16.102.72	Open	277
Johannesburg Internet Exchange	Johannesburg, South Africa	196.60.96.148	Open	217
NAPAfrica IX Durban	Durban, South Africa	196.10.141.51	Open	146
DE-CIX Marseille	Marseille, France	185.1.47.88	Open	113
Durban Internet eXchange	Durban, South Africa	196.223.30.148	Open	104
Asteroid Mombasa	Mombasa, Kenya	196.60.66.19	Open	54
Mauritius Internet Exchange	Ebene, Mauritius	196.223.0.8	Open	27

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.