asn.dev

Interconnection

AS213576 ERTIUS-NET

Unclassified RIPE

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

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
AMS-IX AmsterdamAmsterdam, Netherlands80.249.213.83Open882
The Frys Internet ExchangeFrysian, Netherlands2001:7f8:10f::3:4248:118Open339
Speed Internet ExchangeDronten, Netherlands185.1.223.64Open285
InterIX Internet ExchangeAmsterdam, Netherlands2001:7f8:134::8bOpen234
Local Internet Exchange DüsseldorfDüsseldorf, Germany185.1.155.84—214
Ontario Internet ExchangeToronto, Canada149.112.50.86Open205
Local Internet Exchange FrankfurtFrankfurt, Germany185.1.166.156Open203
Nine IXParis, France185.1.14.133—165
EuroGIX retiredStrasbourg, France185.1.14.133—129
UNMETERED ExchangeVancouver, Canada192.34.27.133Open128
LayerSwitch Internet ExchangeThe Hague, Netherlands185.1.32.142Open104
Local Internet Exchange NetherlandsMeppel, Netherlands185.1.138.60—54

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