Kuancom
KUANCOM
Cluster stats
| Netblocks | 22 |
| Cluster ID | 193208000 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (22)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 27.144.0.0/17 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 27.144.128.0/17 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 42.50.0.0/17 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 42.50.128.0/17 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 42.123.128.0/18 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 42.123.192.0/18 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 117.59.0.0/17 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 117.59.128.0/17 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 125.62.0.0/19 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 125.62.32.0/19 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.161.192.0/20 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.161.208.0/20 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.244.0.0/20 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.244.16.0/20 | KUANCOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 114.54.0.0/16 | KUANCOM | APNIC | ALLOCATED PORTABLE | ● low |
| 114.68.0.0/16 | KUANCOM | APNIC | ALLOCATED PORTABLE | ● low |
| 116.60.0.0/14 | KUANCOM | APNIC | ALLOCATED PORTABLE | ● low |
| 116.60.0.0/16 | KUANCOM | APNIC | ALLOCATED PORTABLE | ● low |
| 117.79.0.0/18 | KUANCOM | APNIC | ALLOCATED PORTABLE | ● low |
| 218.240.64.0 – 218.240.255.255 | KUANCOM | APNIC | ALLOCATED PORTABLE | ● low |
| 219.142.47.32/27 | Kuancom | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 2406:1080::/32 | KUANCOM | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
68.2%
of checked blocks have valid RPKI ROA coverage
(15 of 22)
RPKI-inferred operator
ChongQing Broadcast & TV Transfer Network Co. Ltd
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
AC1601-AP
HC55-AP
HC55-AP
MAINT-CHINANET-BJ
MAINT-CNNIC-AP
SZ345-AP
ZC379-AP
ZM839-AP
ZM839-AP