PJSC Rostelecom

RT-VLD-STATIC-NET-USERS
BGP inherited
Cluster stats
Netblocks6
All fragments 11 blocks across 4 clusters
Cluster ID205950697
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
84.53.201.48 – 84.53.201.79 RT-VLD-STATIC-NET-USERS RIPE ASSIGNED PA ● low
84.53.202.16/28 RT-VLD-STATIC-NET-USERS RIPE ASSIGNED PA ● low
84.53.202.128/28 RT-VLD-STATIC-NET-USERS RIPE ASSIGNED PA ● low
84.53.203.64 – 84.53.203.191 RT-VLD-STATIC-NET-USERS RIPE ASSIGNED PA ● low
84.53.210.0/26 RT-VLD-STATIC-NET-USERS RIPE ASSIGNED PA ● low
84.53.232.0 – 84.53.232.191 RT-VLD-STATIC-NET-USERS RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RT VLD STATIC NET” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT