PJSC Rostelecom

MKS
BGP inherited
Cluster stats
Netblocks10
All fragments 64 blocks across 18 clusters
Cluster ID204545998
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 12 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names 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
116.228.155.60/30 MKS APNIC ASSIGNED NON-PORTABLE ● high
31.13.19.24/29 MKS RIPE ASSIGNED PA ● low
80.255.18.64/27 MKS-NET RIPE ASSIGNED PA ● low
94.25.18.16/29 MKS RIPE ASSIGNED PA ● low
95.167.142.52/30 MKS RIPE ASSIGNED PA ● low
195.151.55.200/30 MKS-GROUP-NET RIPE ASSIGNED PA ● low
212.204.127.248/29 MKS-NET RIPE ASSIGNED PA ● low
212.243.160.208/29 MKS-NET RIPE ASSIGNED PA ● low
217.59.56.80/28 MKS-SRL RIPE ASSIGNED PA ● low
217.112.26.32/27 MKS-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (5 of 10)
No discrepancies found among checked blocks.

NIC Handles

CH-UNISOURCE-MNT DUMY-RIPE DUMY-RIPE INTERB-MNT MAINT-CHINANET-SH MNET-MNT ROSPRINT-NCC ROSTELECOM-MNT RU-MATRIXTELECOM-MNT SGX4-AP SGX4-AP TASCOM-MNT-RIPE