asn.dev

Interconnection

AS56665 TANGO-PROXIMUS_NXT

Residential RIPE Cable/DSL/ISP

Exchanges 13 13 active
Countries 7 most in Germany
Regions 1
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

Europe 13

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.193.156Selective1,078
LINX LON1London, United Kingdom195.66.227.16Selective932
AMS-IX AmsterdamAmsterdam, Netherlands80.249.211.94Selective882
Neutral Internet ExchangeAmsterdam, Netherlands193.239.116.116Selective669
France-IX ParisParis, France37.49.237.46Selective570
DE-CIX DusseldorfDüsseldorf, Germany185.1.170.162Selective227
DE-CIX MunichMunich, Germany185.1.208.162Selective211
DE-CIX HamburgHamburg, Germany185.1.210.161Selective196
Torino Piemonte Exchange PointTorino, Italy194.116.96.247Selective122
Megaport Frankfurt IXFrankfurt, Germany2001:7f8:8:20:0:bd8e:0:1—114
Luxembourg Internet ExchangeLuxembourg, Luxembourg188.93.170.20Selective103
Megaport Dusseldorf IXDüsseldorf, Germany194.146.118.136—98
Belgian National Internet ExchangeBrussels, Belgium194.53.172.17Selective83

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.