MLaB NL: PeeringDB fix list
AS41047 · peeringdb.com/net/14807
4 things to fix in MLaB NL's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on MLaB NL'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 MLaB NL's PeeringDB record. Add one entry per connection with these values.
-
IPv4 – IPv6 2602:fed2:fff:ffff::134 Speed 2000 Mbps (2G) 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.
Correct these entries (3)
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 10G 200G - In the entry with IPv4 185.1.170.47: set Speed to 200000 (200G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 185.1.147.149: set Speed to 1000 (1G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 100M - In the entry with IPv4 193.189.82.238: set Speed to 100 (100M) (now 10000).
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/41047/: 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.