HA-LY-3-RUYANG

BGP inherited
Cluster stats
Netblocks9
All fragments 614 blocks across 18 clusters
Cluster ID210211015
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
123.7.180.7/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.8/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.10/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.12/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.14/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.15/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.16/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.17/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low
123.7.180.21/32 HA-LY-3-RUYANG APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “HA LY 3” — 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 18 name-family clusters →

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

AC1718-AP MAINT-CNCGROUP-HA WW444-AP WW444-AP