Yuansheng

YUANSHENG
Registry
Cluster stats
Netblocks9
All fragments 15 blocks across 7 clusters
Cluster ID211941720
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 22 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
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
101.231.55.148/30 Yuansheng APNIC ASSIGNED NON-PORTABLE ● high
116.228.52.32/30 YUANSHENG APNIC ASSIGNED NON-PORTABLE ● high
116.228.170.24/30 YUANSHENG APNIC ASSIGNED NON-PORTABLE ● high
116.228.215.232/30 YUANSHENG APNIC ASSIGNED NON-PORTABLE ● high
180.169.73.144/29 YUANSHENG APNIC ASSIGNED NON-PORTABLE ● high
218.1.101.16/30 YUANSHENG-CO APNIC ASSIGNED NON-PORTABLE ● high
218.80.193.228/30 YUANSHENG-CO APNIC ASSIGNED NON-PORTABLE ● high
218.80.200.20/30 YUANSHENG-CO APNIC ASSIGNED NON-PORTABLE ● high
112.65.162.132/30 yuansheng APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC1591-AP AC1718-AP HW868-AP HW868-AP LKQ4-AP LKQ4-AP MAINT-CHINANET-SH MAINT-CNCGROUP-SH NW166-AP NW166-AP WLL9-AP WLL9-AP +10 more