Nevigate Communications

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks8
IPv6 2 prefixes (largest 2001:7fa:7:1:0:13:2829:1/128)
Registered in Finland (2) · France (2) · Japan (1) · Singapore (1)
All fragments 110 blocks across 4 clusters
Cluster ID222474551
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

8 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-08-16

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.16.102.217/32 Nevigate Communications PEERINGDB ASSIGNED ● high
210.173.177.143/32 Nevigate Communications PEERINGDB ASSIGNED ● high
2001:7fa:7:1:0:13:2829:1/128 Nevigate Communications PEERINGDB ASSIGNED ● high
2001:de8:12:100::217/128 Nevigate Communications PEERINGDB ASSIGNED ● high
128.127.19.40/29 NET-NEVIGATE RIPE ASSIGNED PA ● low
128.127.19.208/29 NET-NEVIGATE RIPE ASSIGNED PA ● low
192.89.128.144/30 NEVIGATE-NET RIPE ASSIGNED PA ● low
212.213.0.136/29 NEVIGATE-NET RIPE ASSIGNED PA ● low

IPv6 ranges (2)

CIDR
2001:7fa:7:1:0:13:2829:1/128
2001:de8:12:100::217/128

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS132829 DATANET-NOC DUMY-RIPE DUMY-RIPE MYSTREAM-MNT