HAIBO

BGP inherited
Cluster stats
Netblocks7
All fragments 10 blocks across 3 clusters
Cluster ID210075661
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 17 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
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
116.228.49.188/30 HAIBO APNIC ASSIGNED NON-PORTABLE ● high
116.228.208.116/30 HAIBO APNIC ASSIGNED NON-PORTABLE ● high
218.80.216.148/30 HAIBO APNIC ASSIGNED NON-PORTABLE ● high
222.66.89.80/30 HAIBO APNIC ASSIGNED NON-PORTABLE ● high
222.66.94.104/29 HAIBO-CO APNIC ASSIGNED NON-PORTABLE ● high
222.66.198.72/30 HAIBO-CO APNIC ASSIGNED NON-PORTABLE ● high
112.64.184.184/29 haibo APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC1591-AP LZR11-AP LZR11-AP MAINT-CHINANET-SH MAINT-CNCGROUP-SH YQW1-AP YQW1-AP YQW3-AP YQW3-AP YQW7-AP YQW7-AP YR194-AP +5 more