JIAHUA-CO

BGP inherited
Cluster stats
Netblocks9
All fragments 13 blocks across 5 clusters
Cluster ID211868804
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 20 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.29.80/30 JIAHUA-CO APNIC ASSIGNED NON-PORTABLE ● high
116.228.30.12/30 JIAHUA-CO APNIC ASSIGNED NON-PORTABLE ● high
116.228.50.36/30 JIAHUA-CO APNIC ASSIGNED NON-PORTABLE ● high
116.228.227.156/30 JIAHUA-CO APNIC ASSIGNED NON-PORTABLE ● high
116.228.237.204/30 JIAHUA-CO APNIC ASSIGNED NON-PORTABLE ● high
116.236.185.192/30 JIAHUA APNIC ASSIGNED NON-PORTABLE ● high
222.66.146.140/30 JIAHUA-CO APNIC ASSIGNED NON-PORTABLE ● high
222.66.162.96/30 JIAHUA-CO APNIC ASSIGNED NON-PORTABLE ● high
218.106.38.128/25 jiahua-group APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

BH358-AP BH358-AP BH362-AP BH362-AP GGM3-AP GGM3-AP GGM4-AP GGM4-AP HDC8-AP HDC8-AP MAINT-CHINANET-SH MAINT-CN-ZM28 +8 more