JSUNICOM-II
Cluster stats
| Netblocks | 16 |
| All fragments | 19 blocks across 4 clusters |
| Cluster ID | 191853247 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 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
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-06
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 43.226.164.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 43.227.104.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 59.83.192.0/19 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 59.83.224.0/21 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 59.83.232.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 103.45.72.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 103.45.76.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 103.90.92.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 103.142.128.0/23 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 103.211.220.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 114.66.236.0 – 114.66.255.255 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 120.72.32.0/19 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 146.196.68.0/22 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 182.50.8.0/21 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 218.98.0.0/19 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
| 218.98.32.0/19 | JSUNICOM-II | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(12 of 16)
RPKI-inferred operator
CNCGROUP IP network of ShangHai IDC
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
MAINT-CNNIC-AP
YW7053-AP
YW7053-AP