NAP VE - Route Servers
AS64164 · NAP VE
SERVICIOS NAP VEN, C.A.
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 45.68.88.253 45.68.88.254 45.68.88.251 45.68.88.253 45.68.88.254 IPv6 address missing from PeeringDB 2801:18d::253 2801:18d::254 2801:18d::251 2801:18d::253 2801:18d::254 Port speed differs 2 × 20G 10G - 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 4 |
| Nov 18, 2026 | 4 |
| Nov 17, 2026 | 4 |
| Nov 16, 2026 | 4 |
| Nov 15, 2026 | 4 |
| Nov 14, 2026 | 4 |
| Nov 13, 2026 | 4 |
| Nov 12, 2026 | 4 |
| Nov 11, 2026 | 4 |
| Nov 10, 2026 | 4 |
| Nov 9, 2026 | 4 |
| Nov 8, 2026 | 4 |
| Nov 7, 2026 | 4 |
| Nov 6, 2026 | 4 |
| Nov 5, 2026 | 4 |
| Nov 4, 2026 | 4 |
| Nov 3, 2026 | 4 |
| Nov 2, 2026 | 4 |
| Nov 1, 2026 | 4 |
| Oct 31, 2026 | 4 |
| Oct 30, 2026 | 4 |
| Oct 29, 2026 | 4 |
| Oct 28, 2026 | 4 |
| Oct 27, 2026 | 4 |
| Oct 26, 2026 | 4 |
| Oct 25, 2026 | 4 |
| Oct 24, 2026 | 4 |
| Oct 23, 2026 | 4 |
| Oct 22, 2026 | 4 |
| Oct 21, 2026 | 4 |
| Oct 20, 2026 | 4 |
| Oct 19, 2026 | 4 |
| Oct 18, 2026 | 4 |
| Oct 17, 2026 | 4 |
| Oct 16, 2026 | 4 |
| Oct 15, 2026 | 4 |
| Oct 14, 2026 | 4 |
| Oct 13, 2026 | 4 |
| Oct 12, 2026 | 4 |
| Oct 11, 2026 | 4 |
| Oct 10, 2026 | 4 |
| Oct 9, 2026 | 4 |
| Oct 8, 2026 | 4 |
| Oct 7, 2026 | 4 |
| Oct 6, 2026 | 4 |
| Oct 5, 2026 | 4 |
| Oct 4, 2026 | 4 |
| Oct 3, 2026 | 4 |
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.
| NAPVE CCS Caracas, Venezuela | 2 × 20G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| NAPVE MCBO Maracaibo, Venezuela | 2 × 10G | PeeringDB | |
| NAPVE ORI Oriente, Venezuela | 2 × 10G | PeeringDB | |
| NAPVE VLN Valencia, Venezuela | 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.
| Cirion La UrbinaLa Urbina | 1 of 1 | |
| TOP Parque Cristal Los Palos GrandesCaracas | 1 of 1 |