Serverking B.V.: PeeringDB fix list

AS48729 · peeringdb.com/net/43283

PeeringDB

2 things to fix in Serverking B.V.'s PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Serverking 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 (1)

On the exchange's own member list, but not in Serverking B.V.'s PeeringDB record. Add one entry per connection with these values.

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Serverking B.V. has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512Not on its IX-F export
    IPv4185.1.160.223
    IPv62001:7f8:10f::be59:223
    Speed100000 Mbps (100G)

From ixreport.com/net/48729/: 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.