HENGLIAN

BGP inherited
Cluster stats
Netblocks9
All fragments 11 blocks across 3 clusters
Cluster ID212697384
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 19 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name 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.131.100/30 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.120/30 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.124/30 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.128/30 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.132/30 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.136/29 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.144/30 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.148/30 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high
116.228.131.152/29 HENGLIAN APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

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

NIC Handles

MAINT-CHINANET-SH XJQ39-AP XJQ39-AP XJQ40-AP XJQ40-AP XJQ41-AP XJQ41-AP XJQ42-AP XJQ42-AP XJQ43-AP XJQ43-AP XJQ44-AP +7 more