YUANDA

BGP inherited
Cluster stats
Netblocks7
Registered in China (5) · Switzerland (2)
All fragments 16 blocks across 9 clusters
Cluster ID209874742
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 15 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
101.231.79.120/30 YUANDA APNIC ASSIGNED NON-PORTABLE ● high
116.228.200.12/30 YUANDA-CO APNIC ASSIGNED NON-PORTABLE ● high
116.236.210.176/30 YUANDA APNIC ASSIGNED NON-PORTABLE ● high
116.247.94.76/30 YUANDA APNIC ASSIGNED NON-PORTABLE ● high
222.66.49.176/29 YUANDA-CO APNIC ASSIGNED NON-PORTABLE ● high
195.141.68.56/29 YUANDA-NET RIPE ASSIGNED PA ● low
195.141.212.144/28 YUANDA-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “YUANDA” — 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 AS6730-MNT DUMY-RIPE DUMY-RIPE LD1105-AP LD1105-AP LRM4-AP LRM4-AP MAINT-CHINANET-SH WXM26-AP WXM26-AP ZWL25-AP +3 more