Client and local ISP
Your device connects through local Wi-Fi, DNS and an ISP before traffic reaches the subscription entry.
Network routing
Hong Kong transit and Asia-optimized return paths
Understand the network architecture, three-network return-path optimization and the factors that affect real-world performance.
Hong Kong transit
A centralized Hong Kong entry connects the subscription to regional exit resources in Asia, Europe and North America.
Regional exits
Choose and test nodes in the client. Active paths and availability can change with upstream network conditions.
Return-path optimization
Why the return path matters during peak hours
Performance depends on both the outbound path to a server and the path used for replies. If the return route takes an unnecessary detour or reaches a congested international gateway, a seemingly fast node can still show higher latency or unstable video playback.
Selected XunGuangYun Asia routes include return-path optimization for China Telecom, China Unicom and China Mobile directions. The exact path depends on the user's province, ISP, selected node and current upstream conditions.
China Telecom direction
Selected routes use return paths intended to reduce detours for compatible Telecom connections.
China Unicom direction
Selected Asia routes target stable return-path quality for compatible Unicom connections.
China Mobile direction
Selected routes and exits are oriented toward compatible Mobile network paths.
No fixed guarantee
Optimization is a routing advantage, not a guarantee of fixed speed for every ISP, node or time period.
Choosing a route
How to compare nodes
Compare nodes at the same time
Keep your local network and device unchanged so the comparison reflects route differences rather than different test conditions.
Check more than latency
Observe packet loss, web loading, DNS resolution, video startup and sustained throughput instead of relying on a single latency number.
Avoid assuming every node is identical
Nodes use different upstream routes and exits. A regional pool does not mean every endpoint provides the same speed or location reputation.
Troubleshoot all-node failures locally
Update the subscription and verify local network, system time, DNS and client routing before reporting every node as unavailable.
Need troubleshooting steps?
Open troubleshooting guide
Review subscription import, timeout and DNS diagnostics.