asn.dev

Interconnection

AS50272 AVUR AVUR

Residential RIPE

Exchanges 11 11 active
Countries 4 most in Netherlands
Regions 1
Largest fabric 882 AMS-IX Amsterdam

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
AMS-IX AmsterdamAmsterdam, Netherlands80.249.212.82Open882
Giganet Internet ExchangeKyiv, Ukraine185.1.63.73Open355
The Frys Internet ExchangeFrysian, Netherlands2001:7f8:10f::c460:214Open339
Speed Internet ExchangeDronten, Netherlands185.1.222.247Open284
InterIX Internet ExchangeAmsterdam, Netherlands2001:7f8:134::85Open233
LayerSwitch Internet ExchangeThe Hague, Netherlands185.1.32.88Open104
Sweden Open Network Internet eXchange StockholmStockholm, Sweden185.1.215.35Open97
Netnod StockholmStockholm, Sweden195.69.119.204—77
Norwegian Internet Exchange Oslo 1Oslo, Norway185.1.55.13Open68
Free Internet eXchange OsloOslo, Norway91.198.176.34Open42
Netnod Sundsvall- GävleSundsvall, Sweden194.68.128.204Open18

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.