HUANGPU

BGP inherited
Cluster stats
Netblocks7
All fragments 14 blocks across 6 clusters
Cluster ID209663168
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 16 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
101.231.32.44/30 HUANGPU APNIC ASSIGNED NON-PORTABLE ● high
101.231.34.8/30 HUANGPU APNIC ASSIGNED NON-PORTABLE ● high
180.166.101.160/30 HUANGPU APNIC ASSIGNED NON-PORTABLE ● high
180.169.41.164/30 HUANGPU APNIC ASSIGNED NON-PORTABLE ● high
218.80.219.148/30 HUANGPU-CO APNIC ASSIGNED NON-PORTABLE ● high
222.66.75.192/30 HUANGPU-CO APNIC ASSIGNED NON-PORTABLE ● high
222.66.167.236/30 HUANGPU-CO APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “HUANGPU” — 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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP FY371-AP FY371-AP LG888-AP LG888-AP MAINT-CHINANET-SH WZ2615-AP WZ2615-AP YRJ5-AP YRJ5-AP YRJ6-AP YRJ6-AP +4 more