NAP VE - Route Servers: PeeringDB fix list

AS64164 · peeringdb.com/net/36916

PeeringDB

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

Make the changes on NAP VE - Route Servers'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
    IPv4 address missing from PeeringDB45.68.88.253 45.68.88.25445.68.88.251 45.68.88.253 45.68.88.254
    IPv6 address missing from PeeringDB2801:18d::253 2801:18d::2542801:18d::251 2801:18d::253 2801:18d::254
    Port speed differs2 × 20G10G
    • In the entry with IPv4 45.68.88.253: set IPv6 to (empty) (now 2801:18d::253); set Speed to 10000 (10G) (now 20000).
    • In the entry with IPv4 45.68.88.254: set IPv6 to (empty) (now 2801:18d::254); set Speed to 10000 (10G) (now 20000).
    • Add an entry: IPv4 –, IPv6 2801:18d::253, speed 10000 (10G), RS peer no.
    • Add an entry: IPv4 –, IPv6 2801:18d::254, speed 10000 (10G), RS peer no.
    • Add an entry: IPv4 45.68.88.251, IPv6 –, speed 10000 (10G), RS peer no.
    • Add an entry: IPv4 –, IPv6 2801:18d::251, speed 10000 (10G), RS peer no.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

From ixreport.com/net/64164/: 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.