weishengju

Registry
Cluster stats
Netblocks8
All fragments 12 blocks across 4 clusters
Cluster ID211859728
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 16 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
58.242.63.68/30 WEISHENGJU APNIC ASSIGNED NON-PORTABLE ● low
59.32.30.96/30 weishengju APNIC Allocated non-portable ● low
59.44.204.126/32 WeiShengJu APNIC ASSIGNED NON-PORTABLE ● low
59.44.204.170/32 WeiShengJu APNIC ASSIGNED NON-PORTABLE ● low
61.186.219.184/29 weishengju APNIC ASSIGNED NON-PORTABLE ● low
218.26.57.102/32 weishengju APNIC ASSIGNED NON-PORTABLE ● low
222.179.90.168/30 weishengju APNIC ALLOCATED NON-PORTABLE ● low
222.179.142.65/32 weishengju APNIC ALLOCATED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “weishengju” — 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: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

AC2530-AP CC1699-AP CC1699-AP CH445-AP HY-AP IC83-AP MAINT-CHINANET-CQ MAINT-CHINANET-GD MAINT-CHINANET-LN MAINT-CNCGROUP-AH MAINT-CNCGROUP-SX YC1161-AP +4 more