VNPT: PeeringDB fix list
AS45899 · peeringdb.com/net/10647
4 things to fix in VNPT's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on VNPT'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 VNPT's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.162.254.126 IPv6 2001:df6:480::b34b:0:1 Speed 10000 Mbps (10G) RS peer Yes
Correct these entries (2)
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 103.162.254.126 is AS137351 DJASANET 103.162.254.126 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.
-
Problem PeeringDB has The export has Port speed differs 10G 200G - In the entry with IPv4 80.81.192.121: set Speed to 200000 (200G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If VNPT has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.225.30 IPv6 2001:7f8:4::b34b:2 Speed 10000 Mbps (10G)
From ixreport.com/net/45899/: 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.