VPS one-click scripts
All scripts / Beginner guides / read-return-routes
Reading results

How to read return routes

What a return route is

For a VPS outside mainland China, the return route is the path data takes from the machine back into a mainland carrier network — the direction a reply travels when you visit the host from the mainland. The forward and return paths are not always symmetric, so a ping or a forward traceroute is often not enough.

xyz.sh/route --cn traces from the VPS to nine public Telecom / Unicom / Mobile targets in Beijing, Shanghai and Guangzhou, then tries to infer a line type from autonomous systems and known path features.

How to read the 3×3 matrix

On a shared report the back-route is a grid: rows are Beijing, Shanghai and Guangzhou, columns are Telecom, Unicom and Mobile. Each cell is an inferred tag such as CN2-GIA, 163, 9929, 4837, CMIN2 or CMI. Premium paths (CN2 GIA, 9929, CMIN2) are highlighted.

First check whether the carrier you care about is consistent across the three cities. Telecom showing CN2-GIA in every row is usually more reassuring than GIA only in Shanghai with 163 in Beijing — the latter can mean the path changes with the ingress. Then look at the other two carriers: that is what a “three-network optimised” claim actually stands or falls on.

A raw tag or hop count beside a cell is supporting detail for the inference, not an extra score.

An inference is not a guarantee

Tags are heuristic. Temporary detours, load balancing, the chosen target, or tool limits can all affect them. A single CN2-GIA result does not mean every minute of the day or every destination, and it is not a claim that access is fast from everywhere.

An empty, unknown, or very short path means this run could not tell reliably — retry or try another time of day, rather than treating a blank as a line type. To run it yourself: curl -fsSL xyz.sh/route | bash -s -- --cn.

Related