HOSTKEY B.V.: PeeringDB fix list
AS57043 · peeringdb.com/net/8564
4 things to fix in HOSTKEY B.V.'s PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on HOSTKEY B.V.'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 (3)
On the exchange's own member list, but not in HOSTKEY B.V.'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 185.1.192.191 IPv6 2001:7f8:a0::ded3:0:1 Speed 10000 Mbps (10G) RS peer Yes -
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its website members listIPv4 185.1.32.97 IPv6 2001:7f8:8f::a505:7043:1 Speed Not published RS peer Not published
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 6 × 10G 2 × 10G PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/57043/: 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.