asn.dev

Interconnection

AS13768 COGECO-PEER1

Hosting DROP-listed space ARIN

Exchanges 12 12 active
Countries 4 most in United States
Regions 2
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS13768, 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 10 Europe 2

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany2001:7f8::35c8:0:1—1,078
LINX LON1London, United Kingdom195.66.224.156—932
Equinix Internet Exchange AshburnAshburn, United States2001:504:0:2:0:1:3768:1—391
Seattle Internet ExchangeSeattle, United States206.81.80.38—350
Any2 CaliforniaLos Angeles, United States206.72.210.79—319
Toronto Internet ExchangeToronto, Canada206.108.34.159Selective286
Equinix Internet Exchange ChicagoChicago, United States2001:504:0:4:0:1:3768:1—282
Equinix Internet Exchange DallasDallas, United States206.223.118.30—231
New York International Internet ExchangeNew York, United States198.32.160.65Open214
Equinix Internet Exchange MiamiMiami, United States198.32.242.125—178
Equinix Internet Exchange New YorkNew York, United States198.32.118.146—120
Vancouver Internet ExchangeVancouver, Canada206.41.104.1—74

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.