Amsterdam · Netherlands

Amsterdam's routing weight sits in both its exchanges and its buildings. AMS-IX carries 854 participants, ahead of GNM-IX at 440, INTERIX at 213 and BGP.Exchange - Amsterdam at 202, and the remaining exchanges taper down from ERA-IX Amsterdam at 190 to a handful of members each. Colocation adds a second layer, with NIKHEF Amsterdam holding 485 networks and Equinix AM7 holding 215. The carrier registry lists no Dutch mobile operators, so the data cannot say which domestic mobile networks peer here, though AMS-IX counts 29 participant ASNs that the registry recognises as mobile operator networks.

An address that geolocates to Amsterdam may not be a device in Amsterdam. Operators announce address blocks from a registry record, and that record carries one administrative address for an allocation that can be routed anywhere the operator reaches. Mobile traffic leaves through a small number of gateways, so subscribers spread across a country share exit addresses tied to whichever site their operator uses. Geolocation databases follow the operator's own published location, which for an Amsterdam-registered network means Amsterdam even when the user is somewhere else.

Someone checking an address gets more from the origin ASN and the netname on the specific prefix than from a city label. The origin ASN says which network announces the block, and the netname with its registry record says who holds it and how it is described. With 2,400 peering participants and 2,384 networks in Amsterdam buildings, plenty of networks announce space from here without their users being anywhere near it.