Testing a V.PS SG machine I have had for a while; I kept putting off writing the article, and it can be compared with the new product next door for comparison 
Contents
1. Configuration
2. Node Quality
3. Mainland Three-Network Outbound Route Tests
4. Mainland Three-Network TCP Ping
5. Evening Peak Speed Tests
6. International Connectivity
7. Summary
1. Configuration
| Plan | 🇸🇬 V.PS Singapore EPYC Explorer |
|---|---|
| Location | Singapore |
| CPU | 2 x AMD EPYC 7J13 vCPU |
| RAM | 2GB |
| Disk | 30GB |
| Traffic | 1TB(in+out) |
| Route | three-network CN2 GIA return |
| Port Speed | 1Gbps |
| Network | 1 x IPv4, 1 x /64 IPv6 |
| Price | Annual EUR€244.17 |
🔗 Quick Links
| YABS | Node Quality | Mixed Benchmark | nws.sh | Streaming Unlock |
|---|---|---|---|---|
| [Link] | [Link] | [Link] | [Link] | [Link] |
2. Node Quality
bash <(curl -sL https://run.NodeQuality.com)
I originally planned to write a comparison article, so I disabled v6; after thinking about it, I decided to publish the two articles separately.
💻 Basic Information
Performance is very good.
Basic System Information:
---------------------------------
Uptime : 0 days, 1 hours, 9 minutes
Processor : AMD EPYC 7J13 64-Core Processor
CPU cores : 2 @ 2445.414 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 1.9 GiB
Swap : 0.0 KiB
Disk : 30.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 : xTom Pty Ltd
ASN : AS8888 xTom Pty Ltd
Location : Singapore, North West (03)
Country : Singapore
fio Disk Speed Tests (Mixed R/W 50/50) (Partition -):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 471.17 MB/s (117.7k) | 4.76 GB/s (74.4k)
Write | 472.42 MB/s (118.1k) | 4.78 GB/s (74.8k)
Total | 943.60 MB/s (235.8k) | 9.55 GB/s (149.2k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 8.20 GB/s (16.0k) | 8.52 GB/s (8.3k)
Write | 8.64 GB/s (16.8k) | 9.09 GB/s (8.8k)
Total | 16.84 GB/s (32.8k) | 17.62 GB/s (17.2k)
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 1188
Multi Core | 2308
Full Test | https://browser.geekbench.com/v5/cpu/23953774
SysBench CPU Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
1 Thread Test (Single Core) Score: 3635 Scores
2 Thread Test (Multi Core) Score: 7240 Scores
SysBench Memory Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
Single-Thread Read Test: 42657.51 MB/s
Single-Thread Write Test: 25109.44 MB/s
🎬IP Quality
🌐 Network Quality
📍Return Routes
All three networks are forced onto CN2 GIA return routes.
3. Mainland Three-Network Outbound Route Tests (itdog.cn)
China Telecom outbound uses CN2, China Unicom outbound uses 9929, and China Mobile outbound uses CMI.
| Location | China Telecom | China Unicom | China Mobile |
|---|---|---|---|
| Beijing | |||
| Shanghai | |||
| Guangzhou |
4. Mainland Three-Network Outbound TCP Ping (itdog.cn, 2025-12-06 20:00)
During the evening peak, China Telecom and China Unicom are both very stable; China Mobile has somewhat high jitter, while packet loss is acceptable.
| China Telecom | China Unicom | China Mobile |
|---|---|---|
5. Evening Peak Proxy Speed Tests(2025-12-06 22:00)
China Telecom speeds are very good, even a bit higher than the new product next door. China Unicom cross-network latency is a little higher, but speeds still run.
China Mobile cross-network latency is relatively high, but there is still speed; in testing it was not completely QoS-killed.
Telecom
| Node | Average Speed | Maximum Speed | TLS RTT |
|---|---|---|---|
| ShenzhenTelecom@1Gbps | 633.04Mbps | 679.74Mbps | 51ms |
| GuangdongTelecom@1Gbps | 838.67Mbps | 970.65Mbps | 54ms |
| Eastern Guangdong Telecom@1Gbps | 830.91Mbps | 944.78Mbps | 144ms |
| GuangxiTelecom@1Gbps | 411.71Mbps | 455.54Mbps | 69ms |
| HainanTelecom@1Gbps | 400.76Mbps | 423.68Mbps | 60ms |
| ShanghaiTelecom@1Gbps | 709.44Mbps | 817.35Mbps | 73ms |
| Ningbo Telecom@1Gbps | 791.11Mbps | 959.67Mbps | 121ms |
| WenzhouTelecom@1Gbps | 310.43Mbps | 331.76Mbps | 79ms |
| Xi'an Telecom@1Gbps | 742.12bps | 930.44Mbps | 95ms |
Unicom
| Node | Average Speed | Maximum Speed | TLS RTT |
|---|---|---|---|
| GuangdongUnicom@1Gbps | 798.11Mbps | 896.18Mbps | 57ms |
| GuangdongUnicom@2.5Gbps | 878.70bps | 1.01Gbps | 54ms |
| ShanghaiUnicom@1Gbps | 743.75Mbps | 926.52Mbps | 81ms |
| ShaoxingUnicom@1Gbps | 416.66Mbps | 446.99Mbps | 74ms |
| ShandongUnicom@1Gbps | 684.17Mbps | 913.77Mbps | 87ms |
| ShanxiUnicom@1Gbps | 642.73Mbps | 860.56Mbps | 90ms |
| HebeiUnicom@1Gbps | 354.64Mbps | 385.80Mbps | 87ms |
| LiaoningUnicom@1Gbps | 248.99Mbps | 274.00Mbps | 95ms |
Mobile
| Node | Average Speed | Maximum Speed | TLS RTT |
|---|---|---|---|
| Guangzhou Mobile@1Gbps | 150.52Mbps | 187.38Mbps | 75ms |
| Guangxi Mobile@1Gbps | 492.22Mbps | 649.43Mbps | 74ms |
| Shanghai Mobile@1Gbps | 811.35Mbps | 932.77Mbps | 74ms |
| Lishui Mobile@1Gbps | 790.98Mbps | 927.47Mbps | 94ms |
| Jiangsu Mobile@1Gbps | 219.48Mbps | 263.44Mbps | 134ms |
| Hebei Mobile@1Gbps | 470.90Mbps | 599.62Mbps | 126ms |
| Northeast China Mobile@1Gbps | 454.40Mbps | 653.74Mbps | 152ms |
| Shanxi Mobile@1Gbps | 223.30Mbps | 361.98Mbps | 93ms |
| Sichuan Mobile@1Gbps | 264.25Mbps | 331.51Mbps | 92ms |
6. International Connectivity
No real issues. Local 1G ports can be saturated both ways, with latency a few tenths of a millisecond higher than the CTC line.
| Region | Node | Average/Max Upload (Mbps) | Average/Max Download (Mbps) | Latency (ms) |
|---|---|---|---|---|
| 🇸🇬 Singapore | RFCHOST T1 | 1041 / 1072 | 1002 / 1005 | 0.81 |
| 🇸🇬 Singapore | BAGE SG | 1049 / 1082 | 1000 / 1004 | 0.83 |
| 🇸🇬 Singapore | BAGE SGS | 1053 / 1107 | 1001 / 1005 | 1.19 |
| 🇸🇬 Singapore | GreenCloud DC1 | 325 / 639 | 999 / 1004 | 0.35 |
| 🇸🇬 Singapore | GreenCloud DC2 | 1052 / 1084 | 1002 / 1005 | 1.13 |
| 🇸🇬 Singapore | Nube | 1052 / 1099 | 1001 / 1006 | 2.33 |
| 🇸🇬 Singapore | SkylineConnect | 1051 / 1085 | 998 / 1003 | 1.221 |
| 🇸🇬 Singapore | IDC.Care | 904 / 1011 | 900 / 1002 | 1.22 |
| 🇻🇳 Hanoi | GreenCloud | 1015 / 1192 | 957 / 1002 | 54.72 |
| 🇻🇳 Ho Chi Minh City | GreenCloud | 1030 / 1116 | 976 / 1002 | 26.45 |
| 🇮🇳 Mumbai | HostDZire | 419 / 569 | 365 / 539 | 54.20 |
| 🇦🇺 Sydney | GreenCloud | 738 / 993 | 835 / 1004 | 165.45 |
| 🇺🇸 Los Angeles | DMIT T1 | 611 / 818 | 362 / 586 | 165.20 |
| 🇺🇸 Los Angeles | GreenCloud | 1 / 4 | 831 / 1003 | 168.71 |
| 🇺🇸 Los Angeles | AlphaVPS | 0 / 2 | 829 / 1004 | 167.87 |
| 🇺🇸 Los Angeles | BAGE LA1 | 0 / 1 | 519 / 888 | 168.29 |
| 🇺🇸 Los Angeles | BAGE LA2 | 609 / 810 | 647 / 905 | 164.61 |
| 🇺🇸 Los Angeles | RFCHOST T1 | 645 / 813 | 474 / 667 | 168.75 |
| 🇺🇸 San Jose | HostDZire | 781 / 1084 | 827 / 1003 | 174.29 |
| 🇺🇸 San Jose | GreenCloud | 747 / 1082 | 822 / 996 | 174.70 |
| 🇺🇸 San Jose | Nube | 721 / 994 | 787 / 998 | 166.89 |
| 🇺🇸 Seattle | Misaka | 799 / 989 | 856 / 1003 | 148.55 |
| 🇺🇸 Seattle | AlphaVPS | 711 / 914 | 857 / 1003 | 148.56 |
| 🇺🇸 Ogden | GreenCloud | 651 / 897 | 101 / 196 | 207.41 |
| 🇺🇸 Salt Lake City | BAGE | 539 / 812 | 143 / 346 | 183.35 |
| 🇺🇸 Dallas | AlphaVPS | 722 / 903 | 721 / 899 | 198.43 |
| 🇺🇸 Jacksonville | GreenCloud | 630 / 810 | 631 / 811 | 220.46 |
| 🇺🇸 Chicago | GreenCloud DC1 | 471 / 627 | 125 / 290 | 215.38 |
| 🇺🇸 Chicago | GreenCloud DC2 | 727 / 907 | 722 / 901 | 203.00 |
| 🇺🇸 Ashburn | GreenCloud | 595 / 903 | 631 / 865 | 203.42 |
| 🇺🇸 New York | AlphaVPS | 611 / 811 | 596 / 777 | 226.61 |
| 🇩🇪 Frankfurt | BAGE | 585 / 839 | 847 / 1003 | 147.95 |
| 🇩🇪 Frankfurt | GreenCloud | 557 / 905 | 777 / 1003 | 150.19 |
| 🇩🇪 Frankfurt | Nube | 778 / 901 | 854 / 1002 | 150.88 |
| 🇩🇪 Frankfurt | BERO | 625 / 992 | 844 / 1003 | 157.17 |
| 🇩🇪 Nuremberg | Netcup | 163 / 313 | 545 / 752 | 245.17 |
| 🇩🇪 Nuremberg | AlphaVPS | 531 / 784 | 840 / 1003 | 156.66 |
| 🇳🇱 Amsterdam | GreenCloud | 586 / 811 | 832 / 1002 | 156.26 |
| 🇨🇭 Zurich | Aluy | 647 / 896 | 857 / 1002 | 144.29 |
| 🇧🇬 Sofia | AlphaVPS | 319 / 474 | 748 / 918 | 177.54 |
| 🇬🇧 London | AlphaVPS | 508 / 732 | 849 / 1002 | 152.30 |
| 🇬🇧 Coventry | BAGE | 405 / 584 | 549 / 792 | 156.85 |
| 🇬🇧 Coventry | GreenCloud | 575 / 828 | 849 / 1002 | 155.85 |
7. Summary
244 EUR per year is expensive, but it is still a reasonably cost-effective premium Singapore machine for China Telecom. If it were 378/515 EUR per year, the value for individual users would be poor. China Telecom CN2 both ways is good, China Unicom cross-network performance is excellent, China Mobile cross-network is usable, but if you only use China Mobile the price is not worth it. Local connectivity has no issues.
If you need both Hong Kong and Singapore, you can actually buy a Hong Kong CN2 / three-network optimized / Hong Kong outbound dedicated-line machine, then connect it to a Singapore landing node with good Hong Kong-Singapore connectivity. That gives you both speed and value, and costs much less than keeping optimized machines in both Hong Kong and Singapore.
8. About the Tests
The machines used in this test, including all machines used for iPerf3 speed tests, were purchased at my own expense; results may be time-sensitive.
Kernel parameters of the test 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 the mainland Chinapublic-interest speed test service