Bakker IT: PeeringDB fix list
AS44103 · peeringdb.com/net/21424
3 things to fix in Bakker IT's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Bakker IT'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 Bakker IT's PeeringDB record. Add one entry per connection with these values.
-
IPv4 193.189.82.244 IPv6 2001:7f8:33::a104:4103:1 Speed 1000 Mbps (1G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From 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.
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 IPv4 address missing from PeeringDB 185.1.147.115 185.1.147.115 185.1.147.167 IPv6 address missing from PeeringDB 2001:7f8:ca:1::115 2001:7f8:ca:1::115 2001:7f8:ca:1::167 Port speed differs 10G 2 × 1G - In the entry with IPv4 185.1.147.115: set Speed to 1000 (1G) (now 10000).
- Add an entry: IPv4 185.1.147.167, IPv6 2001:7f8:ca:1::167, speed 1000 (1G), RS peer yes.
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/44103/: 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.