DATACOM-NETWORK
Cluster stats
Netblocks10
All fragments 12 blocks across 2 clusters
Cluster ID191928782
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.81.0.0 – 78.81.9.255 DATACOM-NETWORK RIPE ASSIGNED PA ● low
78.81.10.0 – 78.81.127.255 DATACOM-NETWORK RIPE ASSIGNED PA ● low
78.81.192.0/18 DATACOM-NETWORK RIPE ASSIGNED PA ● low
84.242.192.0/19 DATACOM-NETWORK RIPE ASSIGNED PA ● low
84.242.224.0/19 DATACOM-NETWORK RIPE ASSIGNED PA ● low
89.252.64.0/19 DATACOM-NETWORK RIPE ASSIGNED PA ● low
89.252.96.0/19 DATACOM-NETWORK RIPE ASSIGNED PA ● low
213.148.168.0 – 213.148.188.255 DATACOM-NETWORK RIPE ASSIGNED PA ● low
213.148.189.0 – 213.148.190.255 DATACOM-NETWORK RIPE ASSIGNED PA ● low
213.148.191.0/24 DATACOM-NETWORK 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)
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