KUHCC-KCOM
Cluster stats
Netblocks14
Cluster ID192605902
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
14 0 netblocks since 2026-07-05
2026-07-05 peak 14 2026-07-06

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.100.135.64/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.135.92/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.139.80/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.139.124/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.139.128/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.147.140/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.147.184/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.147.228/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.176.56/29 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.184.28/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
83.100.184.100/30 KUHCC-KCOM RIPE ASSIGNED PA ● low
212.50.174.144/29 KUHCC-KCOM RIPE ASSIGNED PA ● low
212.50.189.24/29 KUHCC-KCOM RIPE ASSIGNED PA ● low
213.249.246.112/30 KUHCC-KCOM 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 (14 of 14)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KINGSTON-MNT