lianhe

LIANHE
Registry
Cluster stats
Netblocks8
All fragments 22 blocks across 10 clusters
Cluster ID211850571
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 25 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
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
114.251.34.192/27 LIANHE APNIC ASSIGNED NON-PORTABLE ● high
116.236.216.208/30 LIANHE APNIC ASSIGNED NON-PORTABLE ● high
116.247.102.36/30 LIANHE APNIC ASSIGNED NON-PORTABLE ● high
123.127.189.96/28 LIANHE APNIC ASSIGNED NON-PORTABLE ● high
59.39.67.244/30 LIANHE APNIC Allocated non-portable ● low
60.29.58.144/29 LIANHE-LTD APNIC ASSIGNED NON-PORTABLE ● low
112.65.174.76/30 lianhe APNIC ASSIGNED NON-PORTABLE ● low
219.237.196.224/27 Lianhe-SE APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC1591-AP AC1718-AP AC2798-AP CJ1562-AP CJ1562-AP FS-AP HZ19-AP HZ19-AP IC83-AP LY1735-AP LY1735-AP LY2338-AP +13 more