WUXI WEIFU CORP

WUXI-WEIFU-CORP
Registry
Cluster stats
Netblocks6
All fragments 10 blocks across 5 clusters
Cluster ID210188030
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
218.90.146.136/30 WUXI-WEIFU-CORP APNIC ASSIGNED NON-PORTABLE ● high
218.90.175.136/29 WUXI-WEIFU-CORP APNIC ASSIGNED NON-PORTABLE ● high
222.191.238.32/30 WUXI-WEIFU--CORP APNIC ASSIGNED NON-PORTABLE ● high
222.191.240.212/30 WUXI-WEIFU-CORP APNIC ASSIGNED NON-PORTABLE ● high
58.214.35.20/30 wuxi-weifu-corp APNIC ASSIGNED NON-PORTABLE ● low
218.90.174.80/29 WUXI-weifu-corp APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “WUXI WEIFU” — 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.
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.

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

CH456-AP CH456-AP LJ974-AP LZ826-AP MAINT-CHINANET-JS YG259-AP ZQ380-AP