ixreport

NAP VE - Transit: PeeringDB fix list

AS273890 · peeringdb.com/net/36917

PeeringDB

One thing to fix in NAP VE - Transit's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on NAP VE - Transit'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.

  1. Venezuela NAPVE CCS Caracas, Venezuela · PeeringDB 4524
    ProblemPeeringDB hasThe export has
    Port speed differs200G + 20G400G
    • In the entry with IPv4 45.68.88.1: set Speed to 400000 (400G) (now 200000).
    • In the entry with IPv4 45.68.88.252: set Speed to 400000 (400G) (now 20000).
    • Add an entry: IPv4 –, IPv6 2801:18d::1, speed 400000 (400G), RS peer yes.
    • Add an entry: IPv4 –, IPv6 2801:18d::252, speed 400000 (400G), 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/273890/: 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.