POL-UUES-NET

BGP inherited
Cluster stats
Netblocks6 · 3,450 IPv4 addresses
Cluster ID208835924
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
81.2.37.0 – 81.2.39.255 POL-UUES-NET RIPE ASSIGNED PA ● low
82.162.10.0 – 82.162.13.255 POL-UUES-NET RIPE ASSIGNED PA ● low
82.162.14.0/23 POL-UUES-NET RIPE ASSIGNED PA ● low
86.102.131.0 – 86.102.133.255 POL-UUES-NET RIPE ASSIGNED PA ● low
212.122.16.128/25 POL-UUES-NET RIPE ASSIGNED PA ● low
212.122.17.0/24 POL-UUES-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)
Possible discrepancies (5)

These blocks are registered to POL-UUES-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

82.162.10.0 – 82.162.13.255 /22 authorized for AS12332 — PJSC Rostelecom
81.2.37.0 – 81.2.39.255 /22 authorized for AS12332 — PJSC Rostelecom
86.102.131.0 – 86.102.133.255 /22 authorized for AS12332 — PJSC Rostelecom
82.162.14.0/23 /23 authorized for AS12332 — PJSC Rostelecom
212.122.17.0/24 /24 authorized for AS12332 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE PRIMORYE-NCC-MNT