I heard that CeraNetworks Hong Kong's China Mobile return route was upgraded from CMI to CMIN2, so I tested this model from Rich Lady Host. 
Contents
1. Configuration
2. Node Quality
3. Mainland China three-network outbound route test
4. Mainland China three-network TCP Ping
5. Evening peak speed test
6. International connectivity
7. Summary
1. Configuration
| Plan | 🇭🇰 BestVM Hong Kong BGP-2T |
|---|---|
| Location | China, Hong Kong |
| CPU | 1 x Intel E5-2680v4 vCPU |
| RAM | 1GB |
| Disk | 10GB SSD |
| Traffic | 2TB(in+out) |
| Route | China Mobile CMIN2; China Telecom/Unicom CMI |
| Bandwidth | 10Gbps |
| Network | 1 x IPv4 |
| Price | monthly CNY¥70.00 |
Provider website: https://bestvm.cloud
🔗 Quick links
| YABS | Node Quality | FusionMonster | nws.sh | ping.pe | Streaming unlock |
|---|---|---|---|---|---|
| [Link] | [Link] | [Link] | [Link] | [Link] | [Link] |
The upstream is CERA.
2. Node Quality
bash <(curl -sL https://run.NodeQuality.com)
💻Basic information
Basic System Information:
---------------------------------
Uptime : 0 days, 1 hours, 18 minutes
Processor : Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
CPU cores : 1 @ 2399.996 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 967.9 MiB
Swap : 533.0 MiB
Disk : 11.0 GiB
Distro : Debian GNU/Linux 12 (bookworm)
Kernel : 6.12.57+deb13-cloud-amd64
VM Type : STANDARD PC (I440FX + PIIX, 1996)
IPv4/IPv6 : ✔ Online / ❌ Offline
IPv4 Network Information:
---------------------------------
ISP : Cnservers LLC
ASN : AS40065 CNSERVERS LLC
Host : Cloud Innovation Ltd
Location : Hong Kong, Kowloon ()
Country : Hong Kong
fio Disk Speed Tests (Mixed R/W 50/50) (Partition -):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 206.09 MB/s (51.5k) | 1.77 GB/s (27.6k)
Write | 206.64 MB/s (51.6k) | 1.78 GB/s (27.8k)
Total | 412.74 MB/s (103.1k) | 3.55 GB/s (55.5k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 5.93 GB/s (11.5k) | 6.11 GB/s (5.9k)
Write | 6.25 GB/s (12.2k) | 6.52 GB/s (6.3k)
Total | 12.19 GB/s (23.8k) | 12.63 GB/s (12.3k)
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 724
Multi Core | 721
Full Test | https://browser.geekbench.com/v5/cpu/23947599
SysBench CPU Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
1 Thread Test (Single Core) Score: 904 Scores
SysBench Memory Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
Single-thread Read Test: 19247.08 MB/s
Single-thread Write Test: 14305.63 MB/s
🎬IP quality
Seychelles anycast IP. Geolocation and unlocking both look rather average.
🌐Network quality
📍Return route
Mobile return uses CMIN2, while Telecom and Unicom cross-network return uses CMI.
3. Mainland China three-network outbound tests (itdog.cn)
Telecom outbound uses 163, Unicom outbound seems to use 163 as well, and Mobile outbound uses CMI.
| Location | China Telecom | China Unicom | China Mobile |
|---|---|---|---|
| Beijing | |||
| Shanghai | |||
| Guangzhou |
4. mainland Chinathree networksTCP Ping (itdog.cn,2025-12-03 23:00)
During evening peak, Telecom and Unicom have fairly severe packet loss and jitter, while Mobile has no major issue.
| China Telecom | China Unicom | China Mobile |
|---|---|---|
5. Evening peak proxy speed tests (2025-12-03 22:30-23:30)
Telecom and Unicom cross-network CMI cannot really run. Mobile over CMIN2 is quite good, though the measured latency is a bit high.
*Click the test record to view the speed-test screenshot, including some popular models for comparison.
Telecom
| Node | Average speed | Maximum speed | TLS RTT |
|---|---|---|---|
| ShenzhenTelecom@1Gbps | 10.49Kbps | 87.50Kbps | 44ms |
| GuangdongTelecom@1Gbps | 5.47Kbps | 43.78Kbps | 395ms |
| GuangxiTelecom@1Gbps | 2.99Mbps | 8.58Mbps | 190ms |
| ShanghaiTelecom@1Gbps | 2.54Mbps | 3.33Mbps | 93ms |
| WenzhouTelecom@1Gbps | 61.44Mbps | 97.15Mbps | 100ms |
| NingboTelecom@1Gbps | 42.18Mbps | 64.75Mbps | 108ms |
| JiangsuTelecom@1Gbps | 10.32Mbps | 26.47Mbps | 164ms |
| Xi'anTelecom@1Gbps | 548.15Kbps | 1.01Mbps | 477ms |
Unicom
| Node | Average speed | Maximum speed | TLS RTT |
|---|---|---|---|
| GuangdongUnicom@1Gbps | 5.49Mbps | 21.50Mbps | 166ms |
| GuangdongUnicom@2.5Gbps | 876.04Kbps | 1.74Mbps | 57ms |
| ShanghaiUnicom@1Gbps | 2.77Mbps | 17.40Mbps | 64ms |
| ShaoxingUnicom@1Gbps | 39.84Kbps | 93.67Kbps | 41ms |
| ShanxiUnicom@1Gbps | 16.96Mbps | 79.69Mbps | 65ms |
Mobile
| Node | Average speed | Maximum speed | TLS RTT |
|---|---|---|---|
| GuangzhouMobile@1Gbps | 394.19Mbps | 479.99Mbps | 232ms |
| GuangxiMobile@1Gbps | 766.37Mbps | 912.48Mbps | 60ms |
| ShanghaiMobile@1Gbps | 791.65Mbps | 942.17Mbps | 90ms |
| LishuiMobile@1Gbps | 757.80Mbps | 937.06Mbps | 128ms |
| JiangsuMobile@1Gbps | 257.96Mbps | 631.59Mbps | 138ms |
| HebeiMobile@1Gbps | 772.63Mbps | 943.38Mbps | 93ms |
| ShanxiMobile@1Gbps | 539.39Mbps | 574.25Mbps | 89ms |
| WuhanMobile@1Gbps | 21.09Mbps | 54.39Mbps | 396ms |
| SichuanMobile@1Gbps | 471.63Mbps | 523.52Mbps | 86ms |
6. International connectivity
Various Hong Kong landing nodes can pull it well and approach full speed. Japan and Singapore are also good. HKT seems to return via Europe, causing very high latency. Europe has high latency, low speed, and even traffic drops.
| Region | Node | Average/max upload (Mbps) | Average/max download (Mbps) | Latency (ms) |
|---|---|---|---|---|
| 🇭🇰 Hong Kong | DMIT T1 | 1050 / 1081 | 821 / 941 | 0.88 |
| 🇭🇰 Hong Kong | RFCHOST JINX | 1048 / 1079 | 809 / 941 | 1.07 |
| 🇭🇰 Hong Kong | RFCHOST CTC | 1051 / 1076 | 822 / 938 | 0.83 |
| 🇭🇰 Hong Kong | Nube | 1051 / 1084 | 833 / 994 | 0.93 |
| 🇭🇰 Hong Kong | GreenCloud DC1 | 1051 / 1097 | 818 / 943 | 0.95 |
| 🇭🇰 Hong Kong | GreenCloud DC2 | 1048 / 1069 | 819 / 942 | 0.80 |
| 🇭🇰 Hong Kong | HostHatch | 1049 / 1079 | 818 / 944 | 0.87 |
| 🇭🇰 Hong Kong | YxVM VOL | 1049 / 1089 | 816 / 941 | 1.06 |
| 🇭🇰 Hong Kong | FxTransit | 1050 / 1077 | 816 / 943 | 1.12 |
| 🇭🇰 Hong Kong | Hytron | 1051 / 1077 | 820 / 942 | 0.85 |
| 🇭🇰 Hong Kong | Halo STD | 1049 / 1078 | 821 / 941 | 0.84 |
| 🇭🇰 Hong Kong | Halo Lite | 1051 / 1082 | 821 / 939 | 0.84 |
| 🇭🇰 Hong Kong | BAGE HKS | 1003 / 1019 | 821 / 941 | 0.78 |
| 🇭🇰 Hong Kong | BAGE HKL | 991 / 1014 | 828 / 993 | 0.91 |
| 🇭🇰 Hong Kong | ClawCloud | 1024 / 1087 | 800 / 941 | 3.38 |
| 🇭🇰 Hong Kong | Servps | 943 / 962 | 814 / 942 | 1.44 |
| 🇭🇰 Hong Kong | Boil HKT | 586 / 922 | 908 / 934 | 200.28 |
| 🇭🇰 Hong Kong | Kaze HKBN | 1050 / 1079 | 808 / 937 | 1.84 |
| 🇹🇼 Taipei | Misaka | 1032 / 1147 | 887 / 981 | 18.38 |
| 🇹🇼 Taichung | HiNet | 733 / 871 | 745 / 778 | 51.31 |
| 🇯🇵 Tokyo | DMIT T1 | 992 / 1135 | 907 / 1000 | 45.04 |
| 🇯🇵 Tokyo | BAGE JP | 906 / 1002 | 913 / 1000 | 45.19 |
| 🇯🇵 Tokyo | BAGE JPS | 1013 / 1138 | 965 / 1002 | 45.61 |
| 🇯🇵 Tokyo | Nube | 1016 / 1126 | 909 / 1000 | 49.99 |
| 🇯🇵 Tokyo | GreenCloud SB | 839 / 968 | 964 / 1001 | 45.91 |
| 🇯🇵 Tokyo | GreenCloud IIJ | 657 / 1068 | 852 / 1001 | 46.24 |
| 🇯🇵 Tokyo | RFCHOST T1 | 990 / 1122 | 909 / 1001 | 50.15 |
| 🇯🇵 Tokyo | YxVM VOL | 885 / 1050 | 911 / 1002 | 52.64 |
| 🇯🇵 Tokyo | FxTransit | 121 / 141 | 904 / 1000 | 50.54 |
| 🇰🇷 Seoul | AWS Lightsail | 1028 / 1109 | 915 / 943 | 38.04 |
| 🇸🇬 Singapore | RFCHOST T1 | 1020 / 1127 | 848 / 1002 | 38.22 |
| 🇸🇬 Singapore | BAGE SG | 1034 / 1122 | 891 / 1001 | 30.35 |
| 🇸🇬 Singapore | BAGE SGS | 1020 / 1113 | 848 / 1001 | 30.69 |
| 🇸🇬 Singapore | GreenCloud DC1 | 1019 / 1094 | 781 / 1000 | 30.71 |
| 🇸🇬 Singapore | GreenCloud DC2 | 1025 / 1103 | 756 / 969 | 33.95 |
| 🇸🇬 Singapore | Nube | 961 / 1107 | 732 / 1005 | 31.41 |
| 🇸🇬 Singapore | IDC.Care | 893 / 1005 | 789 / 986 | 37.06 |
| 🇻🇳 Hanoi | GreenCloud | 1040 / 1130 | 896 / 1000 | 21.59 |
| 🇻🇳 Ho Chi Minh City | GreenCloud | 975 / 1075 | 869 / 1001 | 39.88 |
| 🇮🇳 Mumbai | HostDZire | 346 / 507 | 420 / 521 | 94.59 |
| 🇦🇺 Sydney | GreenCloud | 696 / 925 | 743 / 1000 | 143.29 |
| 🇺🇸 Los Angeles | DMIT T1 | 334 / 548 | 42 / 152 | 237.89 |
| 🇺🇸 Los Angeles | GreenCloud | 491 / 670 | 654 / 967 | 143.62 |
| 🇺🇸 Los Angeles | AlphaVPS | 415 / 612 | 672 / 1001 | 147.64 |
| 🇺🇸 Los Angeles | BAGE LA1 | 343 / 524 | 634 / 823 | 152.28 |
| 🇺🇸 Los Angeles | BAGE LA2 | 646 / 866 | 587 / 923 | 143.70 |
| 🇺🇸 Los Angeles | RFCHOST T1 | 239 / 738 | 124 / 672 | 249.63 |
| 🇺🇸 San Jose | HostDZire | 600 / 758 | 683 / 930 | 156.52 |
| 🇺🇸 San Jose | GreenCloud | 426 / 736 | 38 / 125 | 252.59 |
| 🇺🇸 San Jose | Nube | 647 / 913 | 644 / 997 | 148.57 |
| 🇺🇸 Seattle | Misaka | 612 / 756 | 783 / 998 | 141.97 |
| 🇺🇸 Seattle | AlphaVPS | 547 / 834 | 783 / 1002 | 136.42 |
| 🇺🇸 Ogden | GreenCloud | 447 / 725 | 752 / 1000 | 155.24 |
| 🇺🇸 Salt Lake City | BAGE | 673 / 897 | 612 / 830 | 157.77 |
| 🇺🇸 Dallas | AlphaVPS | 346 / 516 | 725 / 1001 | 175.94 |
| 🇺🇸 Jacksonville | GreenCloud | 201 / 409 | 714 / 894 | 198.57 |
| 🇺🇸 Chicago | GreenCloud DC1 | 23 / 39 | 746 / 927 | 185.35 |
| 🇺🇸 Chicago | GreenCloud DC2 | 589 / 916 | 638 / 868 | 253.73 |
| 🇺🇸 Ashburn | GreenCloud | 517 / 889 | 645 / 834 | 208.70 |
| 🇺🇸 New York | AlphaVPS | 351 / 532 | 452 / 743 | 216.16 |
| 🇷🇺 Moscow | Misaka | 602 / 830 | 59 / 114 | 228.80 |
| 🇩🇪 Frankfurt | BAGE | 728 / 960 | 64 / 151 | 193.98 |
| 🇩🇪 Frankfurt | GreenCloud | ERR / ERR | 36 / 80 | 252.62 |
| 🇩🇪 Frankfurt | Nube | 194 / 364 | 59 / 152 | 186.43 |
| 🇩🇪 Frankfurt | BERO | 555 / 919 | 60 / 94 | 206.90 |
| 🇩🇪 Nuremberg | Netcup | 559 / 938 | 54 / 107 | 195.70 |
| 🇩🇪 Nuremberg | AlphaVPS | 605 / 930 | 60 / 124 | 186.55 |
| 🇳🇱 Amsterdam | GreenCloud | 639 / 927 | 37 / 84 | 252.60 |
| 🇨🇭 Zurich | Aluy | ERR / ERR | ERR / ERR | 305.48 |
| 🇧🇬 Sofia | AlphaVPS | 456 / 829 | 61 / 101 | 203.07 |
| 🇬🇧 London | AlphaVPS | 623 / 826 | 64 / 103 | 206.24 |
| 🇬🇧 Coventry | BAGE | ERR / ERR | 55 / 132 | 273.76 |
| 🇬🇧 Coventry | GreenCloud | ERR / ERR | 59 / 115 | 268.59 |
Hong Kong-Japan routes
| 🇭🇰 BestVM <-> 🇯🇵 DMIT | 🇭🇰 BestVM <-> 🇯🇵 BAGE JPS | 🇭🇰 BestVM <-> 🇯🇵 BAGE JP | 🇭🇰 BestVM <-> 🇯🇵 RFCHOST |
|---|---|---|---|
| Outbound | Outbound | Outbound | Outbound |
| Return | Return | Return | Return |
Hong Kong-Singapore routes
Pulling to Singapore is good across the board.
| 🇭🇰 BestVM <-> 🇸🇬 BAGE SGS | 🇭🇰 BestVM <-> 🇸🇬 BAGE SG | 🇭🇰 BestVM <-> 🇸🇬 RFCHOST |
|---|---|---|
| Outbound | Outbound | Outbound |
| Return | Return | Return |
Hong Kong-Europe routes
Neither direction uses RETN, latency is high, and return speed cannot get going, so pulling to Europe is not good. 
| 🇭🇰 BestVM <-> 🇩🇪 Netcup | 🇭🇰 BestVM <-> 🇩🇪 BAGE | 🇭🇰 BestVM <-> 🇬🇧 BAGE |
|---|---|---|
| Outbound | Outbound | Outbound |
| Return | Return | Return |
7. Summary
Currently Mobile users are quite happy, while Telecom and Unicom cross-network access is basically unusable during evening peak. It is effectively single-network optimization. But since Mobile could switch from CMI to CMIN2, it could also switch back, so enjoy it while it lasts. If bought as a discounted plan, the value is good.
Internationally, pulling Hong Kong, Japan, and Singapore is fine; pulling Europe is not good.
8. About the tests
The machines tested in this article, including all machines used for iPerf3 speed tests, were purchased at my own expense. Results may be time-sensitive.
Kernel parameters of the tested machines (/etc/sysctl.conf) are as follows
fs.file-max = 6815744
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_ecn=0
net.ipv4.tcp_frto=0
net.ipv4.tcp_mtu_probing=0
net.ipv4.tcp_rfc1337=0
net.ipv4.tcp_sack=1
net.ipv4.tcp_fack=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_adv_win_scale=1
net.ipv4.tcp_moderate_rcvbuf=1
net.core.rmem_max=33554432
net.core.wmem_max=33554432
net.ipv4.tcp_rmem=4096 87380 33554432
net.ipv4.tcp_wmem=4096 16384 33554432
net.ipv4.udp_rmem_min=8192
net.ipv4.udp_wmem_min=8192
net.ipv4.ip_forward=1
net.ipv4.conf.all.route_localnet=1
net.ipv4.conf.all.forwarding=1
net.ipv4.conf.default.forwarding=1
net.core.default_qdisc=fq
net.ipv4.tcp_congestion_control=bbr
net.ipv6.conf.all.forwarding=1
net.ipv6.conf.default.forwarding=1
9. Acknowledgements
Thanks to “Impart Speed Test“(@Kyoma ) for providing mainland Chinapublic-interest speed-test service