ixreport

NAP VE - Route Servers

AS64164 · NAP VE

SERVICIOS NAP VEN, C.A.

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Route ServerType
OpenPeering policy
0Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with NAP VE - Route Servers? · Where should NAP VE - Route Servers peer next? · Compare NAP VE - Route Servers with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

One thing to fix in NAP VE - Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 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.

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where NAP VE - Route Servers's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 120G across 4 exchanges.

Venezuela NAPVE CCS Caracas, Venezuela 45.68.88.253
45.68.88.254
2801:18d::253
2801:18d::254
2 × 20G Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Venezuela NAPVE MCBO Maracaibo, Venezuela 45.68.89.253
45.68.89.254
2801:18d:0:2000::253
2801:18d:0:2000::254
2 × 10G PeeringDB
Venezuela NAPVE ORI Oriente, Venezuela 45.68.101.253
45.68.101.254
2801:18d:0:3000::253
2801:18d:0:3000::254
2 × 10G PeeringDB
Venezuela NAPVE VLN Valencia, Venezuela 45.68.100.253
45.68.100.254
2801:18d:0:1000::253
2801:18d:0:1000::254
2 × 20G PeeringDB
Facilities (2)

The buildings NAP VE - Route Servers lists in PeeringDB, and how many of the exchanges in each it's on.

Venezuela Cirion La UrbinaLa Urbina 1 of 1
Venezuela TOP Parque Cristal Los Palos GrandesCaracas 1 of 1