uni fuzhou idc1 ChinaUnicom Corp
uni-fuzhou-idc1-ChinaUnicom-Corp
Registry
Cluster stats
| Netblocks | 19 |
| All fragments | 67 blocks across 27 clusters |
| Cluster ID | 206693486 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
19
0 netblocks since 2026-07-05
2026-07-05
peak 19
2026-07-13
IP Ranges (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 58.22.63.192/26 | UNI-FuZhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.100.224/27 | UNI-FuZhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.101.32/27 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.101.64/27 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.101.160/27 | UNI-FuZhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.102.136/29 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.104.196/30 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.104.200/30 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.33/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.34/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.35/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.36/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.37/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.38/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.39/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.40/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.41/32 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.64/28 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 58.22.106.80/28 | uni-fuzhou-idc1-ChinaUnicom-Corp | APNIC | ASSIGNED NON-PORTABLE | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “uni fuzhou idc1” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- UNI-FuZhou-idc1-WangLong-Corp 9 blocks
- UNI-FuZhou-idc1-AiYa-Corp 5 blocks
- UNI-FuZhou-idc1-WenZhouZhongBo-Corp 3 blocks
- UNI-FuZhou-Idc1-FjUnicom-Corp 3 blocks
- UNI-FuZhou-idc1-SouHu-Corp 3 blocks
- UNI-FuZhou-idc1-YiXunNetwork-corp 2 blocks
- UNI-FuZhou-idc1-TianMing-corp 2 blocks
- UNI-FuZhou-idc1-HanDianComputer-Corp 2 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- Fuzhou Idc1 Gaoming Corp via CNCGROUP IP network of ShangHai IDC sub-allocation
- Fuzhou Idc1 Guangfahuafu Security via CNCGROUP IP network of ShangHai IDC sub-allocation
- Fuzhou Idc1 Zhongshihua Corp via CNCGROUP IP network of ShangHai IDC sub-allocation
- Fuzhou Idc1 Yichengnetwork Corp via CNCGROUP IP network of ShangHai IDC sub-allocation
- Fuzhou Idc1 Xiangcai Security via CNCGROUP IP network of ShangHai IDC sub-allocation
- Fuzhou Idc1 Jiudingzhiye Corp via CNCGROUP IP network of ShangHai IDC sub-allocation
- Fuzhou Idc1 Jilixun Corp via CNCGROUP IP network of ShangHai IDC sub-allocation
- Fuzhou Idc1 Dongxing Security via CNCGROUP IP network of ShangHai IDC sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(19 of 19)
No discrepancies found among checked blocks.
NIC Handles
AC1718-AP
JY578-AP
JY578-AP
MAINT-CN-FZ28