NAP VE - Route Servers
Cluster stats
Netblocks16
All fragments 32 blocks across 2 clusters
Cluster ID193391232
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

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

Network trust

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.

NIC Handles

AS64164