SAKHA
Cluster stats
Netblocks13
All fragments 20 blocks across 7 clusters
Cluster ID193993073
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
46.48.128.0 – 46.48.160.255 SAKHA RIPE ASSIGNED PA ● low
46.48.161.0 – 46.48.223.255 SAKHA RIPE ASSIGNED PA ● low
46.48.224.0/19 SAKHA RIPE ASSIGNED PA ● low
80.73.81.0 – 80.73.95.255 SAKHA RIPE ASSIGNED PA ● low
91.185.224.0/21 SAKHA RIPE ASSIGNED PA ● low
91.185.232.0/22 SAKHA RIPE ASSIGNED PA ● low
91.185.236.0/23 SAKHA RIPE ASSIGNED PA ● low
91.185.238.0/24 SAKHA RIPE ASSIGNED PA ● low
91.185.239.0/24 SAKHA RIPE ASSIGNED PA ● low
91.185.240.0/20 SAKHA RIPE ASSIGNED PA ● low
94.245.128.0/19 SAKHA RIPE ASSIGNED PA ● low
213.129.32.0/20 SAKHA RIPE ASSIGNED PA ● low
213.129.48.0/20 SAKHA 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 (13 of 13)
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 ROSTELECOM-MNT SAKHA-MNT