CTCS
Cluster stats
Netblocks16
All fragments 21 blocks across 5 clusters
Cluster ID192064194
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 (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.196.131.0/26 CTCS RIPE ASSIGNED PA ● low
82.196.131.64/26 CTCS RIPE ASSIGNED PA ● low
82.196.132.0/26 CTCS RIPE ASSIGNED PA ● low
82.196.132.64/26 CTCS RIPE ASSIGNED PA ● low
82.196.133.0/26 CTCS RIPE ASSIGNED PA ● low
82.196.133.64/26 CTCS RIPE ASSIGNED PA ● low
82.196.134.0/26 CTCS RIPE ASSIGNED PA ● low
82.196.134.64/26 CTCS RIPE ASSIGNED PA ● low
82.196.135.0/26 CTCS RIPE ASSIGNED PA ● low
82.196.135.64/26 CTCS RIPE ASSIGNED PA ● low
82.196.140.0/24 CTCS RIPE ASSIGNED PA ● low
82.196.141.0/26 CTCS RIPE ASSIGNED PA ● low
82.196.141.64/26 CTCS RIPE ASSIGNED PA ● low
82.196.142.0/24 CTCS RIPE ASSIGNED PA ● low
82.196.143.0/26 CTCS RIPE ASSIGNED PA ● low
82.196.143.64/26 CTCS 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 (16 of 16)
Possible discrepancies (2)

These blocks are registered to CTCS but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

82.196.140.0/24 /24 authorized for AS12389 — PJSC Rostelecom
82.196.142.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

CTCS-MNT DUMY-RIPE DUMY-RIPE