NAP VE - Route Servers

Data as of 2026-09-27

BGP inherited

This organisation

Netblocks	16
IPv6	8 prefixes (largest 2801:18d:0:1000::253/128)
Also registered under this name	32 netblocks across 2 separate records
Record ID	246721602
Registry	PEERINGDB
Customers	see who runs inside this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 1 shared RIR contact/maintainer handle
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (16)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
45.68.88.253/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
45.68.88.254/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
45.68.89.253/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
45.68.89.254/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
45.68.100.253/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
45.68.100.254/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
45.68.101.253/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
45.68.101.254/32	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d::253/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d::254/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d:0:1000::253/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d:0:1000::254/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d:0:2000::253/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d:0:2000::254/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d:0:3000::253/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high
2801:18d:0:3000::254/128	NAP VE - Route Servers	PEERINGDB	ASSIGNED	● high

14 weekly snapshots · JSON

16 0 netblocks since 2026-07-05

2026-07-05 peak 16 2026-09-27

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (16 of 16)

No discrepancies found among checked blocks.

AS64164