WUXI-TELECOM-CONSTRUCT-DEPT
BGP inherited
Cluster stats
| Netblocks | 7 |
| All fragments | 151 blocks across 88 clusters |
| Cluster ID | 212515991 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 58.214.25.0/30 | WUXI-TELECOM-CONSTRUCT-DEPT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.90.158.192/28 | WUXI-TELECOM-CONSTRUCT-DEPT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.90.158.208/28 | WUXI-TELECOM-CONSTRUCT-DEPT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.90.158.224/28 | WUXI-TELECOM-CONSTRUCT-DEPT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.90.158.240/28 | WUXI-TELECOM-CONSTRUCT-DEPT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 58.214.35.120/29 | wuxi-telecom-construct-dept | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 61.160.99.240/28 | WUXI-telecom-construct-dept | APNIC | ASSIGNED NON-PORTABLE | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “WUXI TELECOM” — 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.
- wuxi-telecom-data-dept 12 blocks
- wuxi-telecom-maintenance-dept 8 blocks
- wuxi-telecom-vip-dept 8 blocks
- WUXI-TELECOM-APPRECIATE-DEPT 4 blocks
- WUXI-telecom-luoshe-dept 4 blocks
- WUXI-telecom-business-dept 4 blocks
- wuxi-telecom-corp 3 blocks
- WUXI-telecom-jiangyin-dept 3 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.
- wuxi-jy-telecom-hq-dept via No.31,Jin-rong Street sub-allocation
- WUXI-telecom-meiyuan-dept via No.31,Jin-rong Street sub-allocation
- WUXI-JY-TELECOM-SHIZHUANG-DEPT via No.31,Jin-rong Street sub-allocation
- wuxi-telecom-xinqu-dept via No.31,Jin-rong Street sub-allocation
- SUZHOU-ZJG-TELECOM-WUXIAN2-DEPT via No.31,Jin-rong Street sub-allocation
- WUXI-TELECOM-YELLOWPAPER-DEPT via No.31,Jin-rong Street sub-allocation
- suzhou-SUZHOU-TELECOM-WUXIANG-CORP sub-allocation
- WUXI-telecom-oper-main-dept via No.31,Jin-rong Street sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
57.1%
of checked blocks have valid RPKI ROA coverage
(4 of 7)
No discrepancies found among checked blocks.
NIC Handles
CH456-AP
CH456-AP
JY995-AP
JY996-AP
JY997-AP
JY998-AP
MAINT-CHINANET-JS
RZ264-AP