I previously bought VPS.Town's B1. Back then I heard their large-storage plans offered good value, and this time I had a chance to join the internal beta, so of course I had to test it properly. ac20

International connectivity is in section 5.

1. Configuration

Plan 🇭🇰 VPS.Town A4
Location China, Hong Kong
CPU 2 x AMD EPYC 7B13 vCPU
RAM 4GB
System disk 40GiB SSD
Data disk 1000GiB HDD
Traffic 6144GiB(in+out)
Route international route with no Mainland China optimization
Bandwidth 5Gbps
Network 1 x IPv4

Pricing: 2C4G20G is 29 CNY/month, 4C8G20G is 49 CNY/month; HDD data disk is a one-time purchase at 130 CNY/TB; SSD system disk is 0.1 CNY/GB/month.
A4 has already launched. See the provider post for more promotion details:https://www.nodeseek.com/post-514773-1

🔗 Quick links

YABS NodeQuality nws.sh
Link Link Link

2. Performance tests

2.1 Geekbench 6 30-round loop test

Test tool: Geekbench 6.5; only the GB6 total score and selected subtests were used for data processing

Under high load, performance fluctuations are fairly stable. There are 1-3 drops, but the magnitude is not especially large. The retail version is expected to be system-limited after rounds 9-10, while the performance jitter in this loop test appeared after round 10.

This is an internal beta environment. On the retail version, do not sustain high usage for more than 60 minutes; otherwise, according to the official FAQ, the CPU will be limited to 70% of its original performance. Malicious long-term sustained high usage may result in penalties or termination.

Metric Average Standard deviation
Single-core score 1495.50 15.88
└ Clang compile 1471.37 19.26
└ File compression 1654.00 32.27
└ Text processing 1480.40 32.59
Multi-core score 2739.17 37.73
└ Clang compile 2909.07 47.83
└ File compression 2314.10 37.85
└ Text processing 1732.87 47.14

Test dataset CSV

2.2 YABS fio 100-round loop test

Test tool: YABS.sh fio section, 50/50 mixed read/write
2.2.1 HDD Data disk
  • Bandwidth

  • IOPS

  • Data

+------------+--------+-----------+--------------------+----------+------------------+
| Block Size | Metric | Average MB/s | Std Dev MB/s | Average IOPS | Std Dev IOPS |
+------------+--------+-----------+--------------------+----------+------------------+
| 4k         | Read   |   16.5077 |  0.02019376        |  4099    | 10.00000         |
| 4k         | Write  |   16.5246 |  0.02133996        |  4099    | 10.00000         |
| 4k         | Total  |   33.0352 |  0.04137730        |  8199    | 10.00000         |
| 64k        | Read   |  265.5886 |  0.22039001        |  4100    |  0.00000         |
| 64k        | Write  |  266.9865 |  0.22211734        |  4100    |  0.00000         |
| 64k        | Total  |  532.5794 |  0.44312668        |  8300    |  0.00000         |
| 512k       | Read   | 2778.8288 |  5.37827754        |  5300    |  0.00000         |
| 512k       | Write  | 2929.0496 |  2.01673099        |  5509    | 28.76235         |
| 512k       | Total  | 5708.3904 |  7.33812542        | 10835    | 47.93725         |
| 1m         | Read   | 1500.9792 | 24.23138860        |  1397    | 22.27015         |
| 1m         | Write  | 1601.4336 | 26.35510521        |  1497    | 22.27015         |
| 1m         | Total  | 3108.3520 | 49.36476509        |  2897    | 48.10552         |
+------------+--------+-----------+--------------------+----------+------------------+
2.2.2 SSD System disk
  • Bandwidth

  • IOPS

  • Data
+------------+--------+-----------+------------------+----------+------------------+
| Block Size | Metric | Average MB/s | Std Dev MB/s | Average IOPS | Std Dev IOPS |
+------------+--------+-----------+------------------+----------+------------------+
| 4k         | Read   |  172.1076 |   1.360296       | 42985    | 336.76266        |
| 4k         | Write  |  172.5614 |   1.363783       | 43090    | 337.39944        |
| 4k         | Total  |  344.6724 |   2.724133       | 86125    | 680.66738        |
| 64k        | Read   | 1687.8592 |  27.617336       | 25774    | 418.90188        |
| 64k        | Write  | 1696.4608 |  27.770318       | 25918    | 426.96486        |
| 64k        | Total  | 3388.9280 |  55.562658       | 51741    | 846.99051        |
| 512k       | Read   | 2536.9600 |  14.362204       |  4798    |  20.00000        |
| 512k       | Write  | 2672.8448 |  15.332738       |  5057    |  49.75699        |
| 512k       | Total  | 5215.6416 |  28.603208       |  9912    |  64.00758        |
| 1m         | Read   | 1500.3648 | 113.202594       |  1367    | 115.51816        |
| 1m         | Write  | 1601.2288 | 120.930792       |  1467    | 115.51816        |
| 1m         | Total  | 3105.6896 | 233.663434       |  2926    | 219.55879        |
+------------+--------+-----------+------------------+----------+------------------+

3. Nodequality

🎬IP quality

image

🌐Network quality

During the internal beta, the Lumen outbound route was not yet direct, so latency is higher. You can refer to recent NQ tests on the forum, such as [NodeQuality] VPS.town HKG.A4 freshly released

image

📍Return route

image

4. Internal network bandwidth test

Test tool: iPerf3
Test target: two VPS.Town A4 instances

Internal network traffic is not counted. It is not currently rate-limited and performs very well. After official launch, it will be limited to 5Gbps, while cross-host internal networking will also be enabled.

4.1 Single-thread (30 seconds per run)

Type Average/max download (Mbps) Average/max upload (Mbps) Latency (ms)
🏠 internal network 13377 / 14588 13835 / 15246 0.19
🛜 public network 13236 / 14564 13854 / 14896 0.20

Test records

4.2 Multi-thread (30 seconds per run, 8 threads)

Region Average/max download (Mbps) Average/max upload (Mbps) Latency (ms)
🏠 internal network 25969 / 30040 26091 / 29645 0.19
🛜 public network 26630 / 31132 27563 / 32122 0.22

Test records

5. International connectivity - iPerf3 TCP IPv4 Single-threadspeed test (10 seconds per run, 2025-11-19 21:00-21:30)

Test tool: iPerf3

Local bandwidth can reach 4Gbps+, and international connectivity is also still good.

For Mainland China nodes, you should focus on average/max upload (Mbps), because the mainland side is downloading resources from the remote server.

Region Node Average/max download (Mbps) Average/max upload (Mbps) Latency (ms)
🇨🇳 Mainland China Yunxi Huanjing Guangdong Mobile 1050 / 1710 678 / 818 20.07
🇨🇳 Mainland China Yunxi Huanjing Shandong Unicom 152 / 178 18 / 32 167.82
🇭🇰 Hong Kong DMIT T1 4288 / 4298 3934 / 4078 2.07
🇭🇰 Hong Kong RFCHOST JINX 4298 / 4430 1923 / 1957 0.87
🇭🇰 Hong Kong GreenCloud DC1 4201 / 4439 4748 / 4764 0.62
🇭🇰 Hong Kong GreenCloud DC2 4153 / 4347 4748 / 4776 0.57
🇭🇰 Hong Kong YxVM VOL 4429 / 4482 4734 / 4772 0.76
🇭🇰 Hong Kong Hytron 4440 / 4480 1168 / 1178 0.51
🇭🇰 Hong Kong Halo STD 4463 / 4520 4750 / 4772 0.51
🇭🇰 Hong Kong Halo Lite 4396 / 4474 4737 / 4761 0.60
🇭🇰 Hong Kong BAGE HKS 1048 / 1054 1001 / 1003 0.51
🇭🇰 Hong Kong BAGE HKL 1048 / 1054 990 / 993 0.61
🇭🇰 Hong Kong ClawCloud 1060 / 1126 1019 / 1102 N/A
🇭🇰 Hong Kong Servps 1100 / 2016 918 / 934 1.12
🇭🇰 Hong Kong Boil HKT 904 / 916 909 / 913 1.79
🇹🇼 Taipei Misaka 2494 / 2800 3756 / 4041 16.20
🇯🇵 Tokyo DMIT T1 3420 / 3772 2911 / 3559 45.83
🇯🇵 Tokyo BAGE JP 2650 / 2993 3330 / 3566 44.82
🇯🇵 Tokyo BAGE JPS 2801 / 2994 2907 / 3051 49.06
🇯🇵 Tokyo GreenCloud SB 2754 / 3006 3148 / 3891 49.40
🇯🇵 Tokyo GreenCloud IIJ 2969 / 3485 2049 / 2469 45.51
🇯🇵 Tokyo RFCHOST T1 3349 / 3559 2555 / 2730 49.89
🇯🇵 Tokyo YxVM VOL 2956 / 3158 2795 / 3298 50.34
🇸🇬 Singapore RFCHOST T1 3549 / 3739 2925 / 3064 37.39
🇸🇬 Singapore BAGE SG 3357 / 3900 3398 / 4011 30.20
🇸🇬 Singapore BAGE SGS 3181 / 3554 3954 / 4297 37.77
🇸🇬 Singapore GreenCloud DC1 4037 / 4388 4631 / 4784 30.46
🇸🇬 Singapore GreenCloud DC2 651 / 783 834 / 1018 183.03
🇸🇬 Singapore IDC.Care 878 / 1072 875 / 993 33.76
🇻🇳 Hanoi GreenCloud 3479 / 3667 3086 / 3279 60.87
🇮🇳 Mumbai HostDZire 406 / 510 385 / 522 89.65
🇦🇺 Sydney GreenCloud 930 / 1066 972 / 1128 121.81
🇺🇸 Los Angeles DMIT T1 603 / 1229 830 / 1043 143.63
🇺🇸 Los Angeles GreenCloud LA 1057 / 1239 1056 / 1233 143.52
🇺🇸 Los Angeles BAGE LA1 543 / 780 865 / 1003 143.54
🇺🇸 Los Angeles BAGE LA2 790 / 928 831 / 1000 147.98
🇺🇸 Los Angeles RFCHOST T1 543 / 740 468 / 911 140.54
🇺🇸 San Jose HostDZire 870 / 1102 919 / 1100 161.68
🇺🇸 Seattle Misaka 1143 / 1324 1194 / 1378 134.64
🇷🇺 Moscow Misaka 828 / 1038 687 / 824 163.59
🇩🇪 Frankfurt BAGE 641 / 954 718 / 1028 166.79
🇩🇪 Frankfurt Bero 801 / 997 805 / 989 180.57
🇩🇪 Nuremberg Netcup 896 / 1150 549 / 862 157.26
🇬🇧 Coventry BAGE 407 / 612 326 / 551 202.07

Test records

I have not yet measured a route to Europe that uses RETN (using RETN would not necessarily mean lower latency), but the route to Netcup Nuremberg looks similar in latency to another Hong Kong machine that does use RETN. The route to Misaka Moscow did not use RETN; if it had, latency would not be above 120ms.

Update: according to @Wenxin's reply, the route to Netcup Nuremberg should be using RETN.

VPS.Town to Netcup VPS.Town to Misaka RETN to Netcup RETN to Misaka

6. Intra-Hong Kong connectivity - iPerf3 TCP IPv4 single-thread loop speed test (30 seconds per run, 10 tests in each direction, 2025-11-19 14:30-15:00)

Test tool: iPerf3
Download test: GreenCloud HKG.DC1, peak bandwidth 10Gbps
Upload test: GreenCloud HKG.DC2, peak bandwidth 10Gbps

As you can see, 300-second intra-Hong Kong download/upload tests can still maintain 4Gbps+.

300-second intra-Hong Kong download

Round Average/max download (Mbps) Download traffic(GB) Latency (ms)
Round 1 4299 / 4450 15.0 0.68
Round 2 4159 / 4405 14.5 0.66
Round 3 4006 / 4326 14.0 0.74
Round 4 4183 / 4417 14.6 0.71
Round 5 4087 / 4384 14.3 0.69
Round 6 4210 / 4383 14.7 0.61
Round 7 4297 / 4420 15.0 0.71
Round 8 4228 / 4428 14.8 0.68
Round 9 4238 / 4406 14.8 0.68
Round 10 4170 / 4469 14.6 0.71

Test records

300-second intra-Hong Kong upload

Round Average/max upload (Mbps) Upload traffic(GB) Latency (ms)
Round 1 4623 / 4774 16.1 0.62
Round 2 4690 / 4773 16.4 0.69
Round 3 4666 / 4774 16.3 0.69
Round 4 4648 / 4772 16.2 0.59
Round 5 4660 / 4774 16.3 0.68
Round 6 4633 / 4776 16.2 0.72
Round 7 4602 / 4777 16.1 0.57
Round 8 4627 / 4773 16.2 0.59
Round 9 4648 / 4774 16.2 0.69
Round 10 4692 / 4774 16.4 0.65

Test records

7. Speedtest Multi-threadspeed test

curl -sL nws.sh | bash
---------------------------------- nws.sh ---------------------------------
      A simple script to bench network performance using speedtest-cli     
---------------------------------------------------------------------------
 Speedtest.net (Region: GLOBAL)
---------------------------------------------------------------------------
 Location         Latency     Loss    DL Speed       UP Speed       Server      

 ISP: Suzhou Yesong Information Technology Co. 

 Nearest          0.39 ms     0.0%    4470.85 Mbps   4767.83 Mbps   fdcservers.net - Hong Kong 

 Bangalore, IN    69.37 ms    0.0%    3377.51 Mbps   1128.46 Mbps   Bharti Airtel Ltd - Bangalore 
 Chennai, IN      76.71 ms    0.0%    3190.55 Mbps   1284.32 Mbps   RailTel Corporation of India Ltd - Chennai 
 Mumbai, IN       103.97 ms   0.0%    4345.25 Mbps   3044.31 Mbps   Melbicom - Mumbai 

 Seattle, US      142.36 ms   N/A     922.61 Mbps    630.18 Mbps    Comcast - Seattle, WA 
 Los Angeles, US  147.30 ms   0.0%    3417.31 Mbps   343.14 Mbps    ReliableSite Hosting - Los Angeles, CA 
 Dallas, US       183.84 ms   0.0%    2427.70 Mbps   1801.37 Mbps   Hivelocity - Dallas, TX 
 Miami, US        200.81 ms   0.0%    2832.97 Mbps   1620.87 Mbps   Frontier - Miami, FL 
 New York, US     181.89 ms   0.0%    4487.40 Mbps   1840.18 Mbps   GSL Networks - New York, NY 
 Toronto, CA      197.43 ms   0.0%    937.22 Mbps    448.84 Mbps    Rogers - Toronto, ON 
 Mexico City, MX  203.64 ms   N/A     1014.94 Mbps   434.66 Mbps    INFINITUM - Ciudad de México 

 London, UK       185.19 ms   0.0%    4191.37 Mbps   1777.03 Mbps   VeloxServ Communications - London 
 Amsterdam, NL    174.10 ms   0.0%    4494.64 Mbps   1174.34 Mbps   31173 Services AB - Amsterdam 
 Paris, FR        186.58 ms   0.0%    4404.89 Mbps   1954.57 Mbps   Scaleway - Paris 
 Frankfurt, DE    180.02 ms   0.0%    2608.26 Mbps   511.20 Mbps    Clouvider Ltd - Frankfurt am Main 
 Warsaw, PL       249.16 ms   0.0%    3598.40 Mbps   1387.64 Mbps   Play - Warszawa 
 Bucharest, RO    212.93 ms   0.0%    3336.44 Mbps   1689.51 Mbps   Digi        
 Moscow, RU       164.92 ms   0.0%    4233.79 Mbps   1852.37 Mbps   Misaka Network, Inc. - Moscow 

 Jeddah, SA       138.92 ms   0.0%    4217.79 Mbps   2090.40 Mbps   Saudi Telecom Company 
 Dubai, AE        121.13 ms   N/A     4131.58 Mbps   3075.98 Mbps   e& UAE - Dubai 
 Istanbul, TR     220.44 ms   0.0%    3988.27 Mbps   1608.48 Mbps   Turkcell - Istanbul 
 Tehran, IR       248.74 ms   0.0%    1261.46 Mbps   349.34 Mbps    Irancell - Tehran 
 Cairo, EG        209.95 ms   0.0%    1078.43 Mbps   417.90 Mbps    Telecom Egypt - Cairo 

 Tokyo, JP        53.82 ms    67.8%   2229.15 Mbps   796.44 Mbps    fdcservers.net - Tokyo 
 Shanghai, CU-CN  290.92 ms   N/A     77.75 Mbps     858.35 Mbps    China Unicom 5G - Shanghai 
 Hong Kong, CN    0.61 ms     0.0%    4471.26 Mbps   1197.08 Mbps   Misaka Network, Inc. - Hong Kong 
 Singapore, SG    39.54 ms    0.0%    3809.42 Mbps   2528.53 Mbps   ViewQwest - Singapore 
 Jakarta, ID      105.07 ms   3.0%    1379.82 Mbps   584.94 Mbps    PT Solnet Indonesia - Jakarta 

 Sydney, AU       129.41 ms   0.0%    4388.97 Mbps   2515.04 Mbps   Aussie Broadband - Sydney 
---------------------------------------------------------------------------
 Avg DL Speed       : 3080.21 Mbps
 Avg UL Speed       : 1507.35 Mbps

 Total DL Data      : 120.50 GB
 Total UL Data      : 56.43 GB
 Total Data         : 176.93 GB
---------------------------------------------------------------------------
 Duration           : 14 min 35 sec
 System Time        : 18/11/2025 - 07:50:11 UTC
 Total Script Runs  : 508987
---------------------------------------------------------------------------
 Result             : https://result.nws.sh/r/1763451294_D29DHH_GLOBAL.txt
---------------------------------------------------------------------------

8. Summary

If A4 launches at the expected price, it will be a very cost-effective choice: large port capacity, cheap storage, and good performance. China Mobile can use Lumen direct routing, which is a plus for a large-storage plan. However, after official launch, the actual China Mobile direct-route effect will still depend on region and congestion.

9. About the tests

VPS.Town A4 2C4G40G” and ”VPS.Town A4 2C4G40G + 1TB HDD” are internal beta machines entrusted by the provider for testing, and are not guaranteed to match the retail-version experience. The other 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

10. Acknowledgements

Thanks to VPS.Town for providing two machines for testing.