Vilcom Networks Limited: PeeringDB fix list
AS329014 · peeringdb.com/net/31155
One thing to fix in Vilcom Networks Limited's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Vilcom Networks Limited'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 Address belongs to another network in PeeringDB 196.223.21.156 is AS329504 Vlicom Networks Limited 196.223.21.156 Address belongs to another network in PeeringDB 2001:43f8:60:1::156 is AS329504 Vlicom Networks Limited 2001:43f8:60:1::156 IPv4 address in PeeringDB, not in the export 196.223.21.208 196.223.21.156 IPv6 address in PeeringDB, not in the export 2001:43f8:60:1::208 2001:43f8:60:1::156 Port speed differs 10G 2 × 10G An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 196.223.21.208: set IPv4 to (empty) (now 196.223.21.208); set IPv6 to (empty) (now 2001:43f8:60:1::208).
From ixreport.com/net/329014/: 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.