NAP VE - Transit
Cluster stats
Netblocks16
All fragments 32 blocks across 2 clusters
Cluster ID191871711
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.1/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
45.68.88.252/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
45.68.89.1/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
45.68.89.252/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
45.68.100.1/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
45.68.100.252/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
45.68.101.1/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
45.68.101.252/32 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d::1/128 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d::252/128 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d:0:1000::1/128 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d:0:1000::252/128 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d:0:2000::1/128 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d:0:2000::252/128 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d:0:3000::1/128 NAP VE - Transit PEERINGDB ASSIGNED ● high
2801:18d:0:3000::252/128 NAP VE - Transit 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

AS273890