LSIX IX Route Servers: PeeringDB fix list
AS49917 · peeringdb.com/net/10253
3 things to fix in LSIX IX Route Servers's PeeringDB record, from what its exchanges publish: 2 to add, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on LSIX IX Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (2)
On the exchange's own member list, but not in LSIX IX Route Servers's PeeringDB record. Add one entry per connection with these values.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 – IPv6 2001:7f8:8e:4::3d Speed 10000 Mbps (10G) RS peer Yes
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If LSIX IX Route Servers has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308Not on its IX-F export or website members listIPv4 185.1.32.253 IPv6 2001:7f8:8f::a504:9917:2 Speed 10000 Mbps (10G) IPv4 185.1.32.254 IPv6 2001:7f8:8f::a504:9917:1 Speed 10000 Mbps (10G)
From ixreport.com/net/49917/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.