VNET a.s.: PeeringDB fix list
AS29405 · peeringdb.com/net/3926
4 things to fix in VNET a.s.'s PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on VNET a.s.'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 (4)
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 2.5G 2G - In the entry with IPv4 193.188.137.24: set Speed to 2000 (2G) (now 2500).
-
Problem PeeringDB has The export has Port speed differs 25G 100G - In the entry with IPv4 80.81.193.133: set Speed to 100000 (100G) (now 25000).
-
Problem PeeringDB has The export has Port speed differs 25G 100G - In the entry with IPv4 91.210.17.33: set Speed to 100000 (100G) (now 25000).
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 IPv4 address missing from PeeringDB 194.30.187.6 194.30.187.5 194.30.187.6 IPv6 address missing from PeeringDB 2001:7f8:91::3:2 2001:7f8:91::3:1 2001:7f8:91::3:2 Port speed differs 25G 50G - In the entry with IPv4 194.30.187.6: set Speed to 50000 (50G) (now 25000).
- Add an entry: IPv4 194.30.187.5, IPv6 2001:7f8:91::3:1, speed 50000 (50G), 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/29405/: 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.