POL-NAKHODKA-NET

BGP inherited
Cluster stats
Netblocks6 · 4,858 IPv4 addresses
Cluster ID208942210
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.162.224.0 – 82.162.229.255 POL-NAKHODKA-NET RIPE ASSIGNED PA ● low
82.162.232.0/23 POL-NAKHODKA-NET RIPE ASSIGNED PA ● low
82.162.234.0/23 POL-NAKHODKA-NET RIPE ASSIGNED PA ● low
86.102.146.0 – 86.102.148.255 POL-NAKHODKA-NET RIPE ASSIGNED PA ● low
86.102.220.0/22 POL-NAKHODKA-NET RIPE ASSIGNED PA ● low
212.91.218.0/23 POL-NAKHODKA-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
RPKI-inferred operator PJSC Rostelecom
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE PRIMORYE-NCC-MNT