Interconnection

AS35625 EUROFIBER-FRANCE

Hosting RIPE

Exchanges 14 13 active

Countries 5 most in France

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 AS35625, 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 14

Exchange	Location	Their address	Policy	Member ports
DE-CIX Frankfurt	Frankfurt, Germany	80.81.197.197	Open	1,078
France-IX Paris	Paris, France	37.49.236.24	Open	570
Equinix Internet Exchange Paris	Paris, France	195.42.144.43	Open	236
DE-CIX Dusseldorf	Düsseldorf, Germany	185.1.170.247	Open	227
DE-CIX Madrid	Madrid, Spain	185.1.192.205	Open	227
DE-CIX Munich	Munich, Germany	185.1.208.224	Open	211
DE-CIX Hamburg	Hamburg, Germany	185.1.210.219	Open	196
Nine IX	Paris, France	185.1.14.20	—	164
EuroGIX retired	Strasbourg, France	185.1.14.54	—	129
DE-CIX Marseille	Marseille, France	185.1.47.136	Open	113
Luxembourg Internet Exchange	Luxembourg, Luxembourg	188.93.170.85	—	103
France-IX Lyon	Lyon, France	77.95.71.104	—	94
CERN IXP / Equinix Internet Exchange Geneva	Geneva, Switzerland	192.65.185.95	Open	55
DE-CIX Barcelona	Barcelona, Spain	185.1.119.44	Open	49

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-12 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,167 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.