CTSRND-NET
Cluster stats
Netblocks12
Cluster ID191928161
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

Footprint over time

2 weekly snapshots · JSON
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-06

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.66.160.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
77.66.161.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.96.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.105.0 – 80.80.111.255 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.113.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.114.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.115.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.118.0/23 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.124.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.125.0/24 CTSRND-NET RIPE ASSIGNED PA ● low
80.80.126.0/23 CTSRND-NET RIPE ASSIGNED PA ● low
213.27.42.0/23 CTSRND-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (10 of 12)
RPKI-inferred operator MTS PJSC
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 KUBANGSM-MNT