asn.dev

Interconnection

AS37119 unitel-AS

Unclassified AFRINIC

Exchanges 11 9 active
Countries 6 most in Angola
Regions 4
Largest fabric 939 IX.br (PTT.br) Fortaleza

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS37119, 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 5 Europe 3 North America 2 Latin America 1

ExchangeLocationTheir addressPolicyMember ports
IX.br (PTT.br) FortalezaFortaleza, Brazil45.68.73.143—939
LINX LON1London, United Kingdom195.66.224.166Selective931
NAPAfrica IX JohannesburgJohannesburg, South Africa196.60.11.18Selective603
NAPAfrica IX Cape TownCape Town, South Africa196.60.71.25Selective311
Equinix Internet Exchange MiamiMiami, United States198.32.242.66Selective178
DE-CIX LisbonLisbon, Portugal185.1.131.32Selective63
Gigabit Portuguese Internet Exchange PointLisbon, Portugal193.136.250.185Selective63
ANGONIXLuanda, Angola196.11.234.4Selective38
AngolaIXP - Angola Internet Exchange PointLuanda, Angola196.223.1.23Selective24
Equinix-LA(former Paix) retiredLos Angeles, United States198.32.242.66Selective—
Ponto de Intercambio Internet Angola retiredLuanda, Angola196.223.1.23Selective—

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.