lisheng

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
116.228.188.224/30 LISHENG APNIC ASSIGNED NON-PORTABLE ● high
180.169.86.152/30 LISHENG APNIC ASSIGNED NON-PORTABLE ● high
222.66.198.252/30 LISHENG-CO APNIC ASSIGNED NON-PORTABLE ● high
58.252.72.174/32 lisheng APNIC ASSIGNED NON-PORTABLE ● low
58.252.73.186/32 lisheng APNIC ASSIGNED NON-PORTABLE ● low
121.9.217.240/30 lisheng APNIC Allocated non-portable ● low
221.4.159.130/32 lisheng APNIC ASSIGNED NON-PORTABLE ● low
221.4.159.131/32 lisheng APNIC ASSIGNED NON-PORTABLE ● low
221.4.159.132/32 lisheng APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “lisheng” — 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 →
77.8% of checked blocks have valid RPKI ROA coverage (7 of 9)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP AC1718-AP CG272-AP CG272-AP FS-AP IC83-AP MAINT-CHINANET-GD MAINT-CHINANET-SH MAINT-CNCGROUP-GD ML1748-AP ML1748-AP PJJ2-AP +3 more