Navice Communications B.V.: PeeringDB fix list
AS38230 · peeringdb.com/net/26524
2 things to fix in Navice Communications B.V.'s PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on Navice Communications 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.
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 1G 200G - In the entry with IPv4 185.1.170.138: set Speed to 200000 (200G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Navice Communications B.V. has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2001:7f8:11f:be00:38:230:0:1 Speed Not published This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/38230/: 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.