asn.dev

Interconnection

AS18678 INTERNEXA S.A. E.S.P

Unclassified LACNIC

Exchanges 9 9 active
Countries 5 most in United States
Regions 3
Largest fabric 882 AMS-IX Amsterdam

Recorded presence

Internet exchanges

recorded

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

North America 5 Latin America 3 Europe 1

ExchangeLocationTheir addressPolicyMember ports
AMS-IX AmsterdamAmsterdam, Netherlands80.249.214.93Selective882
Equinix Internet Exchange AshburnAshburn, United States2001:504:0:2:0:26:2589:1Selective391
Coresite - Any2 WestLos Angeles, United States206.72.210.97Selective344
New York International Internet ExchangeNew York, United States198.32.160.173Selective214
FL-IX - The Florida Internet Exchange / Community IX - FloridaMiami, United States206.41.108.77Open181
Equinix Internet Exchange MiamiMiami, United States198.32.243.208—178
PIT Chile - SantiagoSantiago, Chile45.68.16.97Selective170
PIT Lima - PIT PeruLima, Peru45.183.47.111Selective120
PIT Colombia - BogotaBogota, Colombia45.68.24.147—69

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.