PJSC Rostelecom

POL-001-NET
BGP inherited
Cluster stats
Netblocks10
All fragments 3,572 blocks across 2,299 clusters
Cluster ID208039511
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-13

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
212.107.194.0/28 POL-001-NET RIPE ASSIGNED PA ● low
212.107.197.0/28 POL-001-NET RIPE ASSIGNED PA ● low
212.107.204.0/28 POL-001-NET RIPE ASSIGNED PA ● low
212.107.206.0/28 POL-001-NET RIPE ASSIGNED PA ● low
212.107.208.0/28 POL-001-NET RIPE ASSIGNED PA ● low
212.107.210.0/27 POL-001-NET RIPE ASSIGNED PA ● low
212.107.218.0/25 POL-001-NET RIPE ASSIGNED PA ● low
212.122.0.0/23 POL-001-NET RIPE ASSIGNED PA ● low
212.122.2.0/24 POL-001-NET RIPE ASSIGNED PA ● low
212.122.3.0/24 POL-001-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 (10 of 10)
Possible discrepancies (3)

These blocks are registered to POL-001-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.

212.122.0.0/23 /23 authorized for AS12332 — PJSC Rostelecom
212.122.2.0/24 /24 authorized for AS12332 — PJSC Rostelecom
212.122.3.0/24 /24 authorized for AS12332 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE PRIMORYE-NCC-MNT ROSNIIROS-MNT