Yi Hong

YIHONG
Registry
Cluster stats
Netblocks7
All fragments 10 blocks across 4 clusters
Cluster ID211936601
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 21 shared RIR contact/maintainer handles
Registry names 4 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.43.48/29 YIHONG APNIC ASSIGNED NON-PORTABLE ● high
101.231.223.52/30 YIHONG APNIC ASSIGNED NON-PORTABLE ● high
180.168.179.64/30 YIHONG APNIC ASSIGNED NON-PORTABLE ● high
218.80.1.77/32 YIHONG APNIC ASSIGNED NON-PORTABLE ● high
58.246.124.164/30 YiHong APNIC ASSIGNED NON-PORTABLE ● low
58.252.72.199/32 yihong APNIC ASSIGNED NON-PORTABLE ● low
60.28.55.232/29 YIHONG-LTD APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC1591-AP AC1718-AP AC2798-AP CG272-AP CG272-AP HZ19-AP HZ19-AP LXR134-AP LXR134-AP LXR166-AP LXR166-AP LXR350-AP +9 more