WAWO Host PIS 318 CNY/Year Hong Kong Direct Optimized Routing | Evening Peak Speed Tests | International Connectivity | Review

I got into this scene relatively late. WAWO used to have a strong reputation, and recently it also received a provider badge on the forum, so I tested its PIS product to see how it performs.

Contents

1. Configuration
2. Node Quality and Mixed Benchmark
3. Mainland Three-Network Outbound Route Tests
4. Mainland Three-Network TCP Ping
5. Evening Peak Direct Single-Thread Speed Tests
6. International Connectivity
7. Summary

1. Configuration

🔗 Quick Links

The upstream is Landups, said to be strong with both small and large packets, but let's test it first.

2. Node Quality and Mixed Benchmark

bash <(curl -sL https://run.NodeQuality.com)

Native Hong Kong IP, good unlock.
PIS seems unfriendly to NQ traceroute and mainland China test nodes, so they could not be measured; the mixed benchmark appears to show Telecom CN2 GIA, Unicom 4837->10099, and Mobile CMIN2.

💻 Basic Information

Basic System Information:
---------------------------------
Uptime     : 0 days, 20 hours, 34 minutes
Processor  : Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
CPU cores  : 2 @ 2394.454 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 1.9 GiB
Swap       : 0.0 KiB
Disk       : 21.0 GiB
Distro     : Debian GNU/Linux 12 (bookworm)
Kernel     : 6.12.57+deb13-cloud-amd64
VM Type    : STANDARD PC (Q35 + ICH9, 2009)
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : Landups Limited
ASN        : AS150452 LANDUPS LIMITED
Host       : Landups Limited
Location   : Mong Kok, Yau Tsim Mong District (KYT)
Country    : Hong Kong

fio Disk Speed Tests (Mixed R/W 50/50) (Partition -):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 233.02 MB/s  (58.2k) | 1.35 GB/s    (21.2k)
Write      | 233.63 MB/s  (58.4k) | 1.36 GB/s    (21.3k)
Total      | 466.65 MB/s (116.6k) | 2.72 GB/s    (42.5k)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 638.79 MB/s   (1.2k) | 573.97 MB/s    (560)
Write      | 672.74 MB/s   (1.3k) | 612.19 MB/s    (597)
Total      | 1.31 GB/s     (2.5k) | 1.18 GB/s     (1.1k)

Geekbench 5 Benchmark Test:
---------------------------------
Test            | Value                         
                |                               
Single Core     | 586                           
Multi Core      | 1198                          
Full Test       | https://browser.geekbench.com/v5/cpu/23965783

 SysBench CPU Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
 1 Thread Test (Single Core) Score:          758 Scores
 2 Thread Test (Multi Core) Score:          1615 Scores
 SysBench Memory Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
 Single-Thread Read Test:          18064.12 MB/s
 Single-Thread Write Test:          13867.95 MB/s

🎬IP Quality	🌐 Network Quality	📍Return Routes

Mixed Benchmark

export noninteractive=true && curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && ./goecs.sh install && goecs

------------------------------------Upstream and Return Route Check-------------------------------------
Beijing Telecom v4 219.141.140.10           Telecom CN2GIA [Premium Route] Telecom CTGNET [Premium Route] 
Beijing Unicom v4 202.106.195.68           Unicom 4837   [Normal Route] 
Beijing Mobile v4 221.179.155.161          Mobile CMI    [Normal Route] Mobile CMIN2  [Premium Route] 
Shanghai Telecom v4 202.96.209.133           Telecom CN2GIA [Premium Route] Telecom CTGNET [Premium Route] 
Shanghai Unicom v4 210.22.97.1              Unicom 4837   [Normal Route] 
Shanghai Mobile v4 211.136.112.200          Mobile CMI    [Normal Route] Mobile CMIN2  [Premium Route] 
Guangzhou Telecom v4 58.60.188.222            Telecom CN2GIA [Premium Route] Telecom CTGNET [Premium Route] 
Guangzhou Unicom v4 210.21.196.6    Unable to detect the IPv4 address of the return-route node
Guangzhou Mobile v4 120.196.165.24           Mobile CMI    [Normal Route] Mobile CMIN2  [Premium Route] 
Chengdu Telecom v4 61.139.2.69              Telecom CN2GIA [Premium Route] 
Chengdu Unicom v4 119.6.6.6                Unicom 4837   [Normal Route] 
Chengdu Mobile v4 211.137.96.205           Mobile CMI    [Normal Route] Mobile CMIN2  [Premium Route] 
Beijing Telecom v6 2400:89c0:1053:3::69     Telecom 163    [Normal Route] 
Beijing Unicom v6 2400:89c0:1013:3::54     Unicom 4837   [Normal Route] 
Beijing Mobile v6 2409:8c00:8421:1303::55  Mobile CMIN2  [Premium Route] Mobile CMI    [Normal Route] 
Shanghai Telecom v6 240e:e1:aa00:4000::24    Telecom 163    [Normal Route] 
Shanghai Unicom v6 2408:80f1:21:5003::a     Unicom 4837   [Normal Route] 
Shanghai Mobile v6 2409:8c1e:75b0:3003::26  Mobile CMIN2  [Premium Route] Mobile CMI    [Normal Route] 
Guangzhou Telecom v6 240e:97c:2f:3000::44     Telecom 163    [Normal Route] 
Guangzhou Unicom v6 2408:8756:f50:1001::c    Unicom 4837   [Normal Route] 
Guangzhou Mobile v6 2409:8c54:871:1001::12   Mobile CMI    [Normal Route] Mobile CMIN2  [Premium Route] 
Check detailed routes yourself for the exact path; this test result is for reference only
When multiple routes appear for the same target address, detection may have passed the aggregation layer; information after the first route may be invalid
-------------------------------------Three-Network Return Route Check-------------------------------------
[NextTrace API] preferred API IP - 172.67.69.163 - 236.67ms - Misaka.BER
Guangzhou Telecom - ICMP v4 - traceroute to 58.60.188.222, 30 hops max, 52 byte packets
0.54 ms      AS152918   *                  China, Hong Kong, cdn.liberally.network 
1.24 ms      *          *                  *
0.90 ms      *          *                  *
1.32 ms      *          *                  *
1.26 ms      AS23764    [CTHKI-HK]         China, Hong Kong, chinatelecomglobal.com  Telecom
2.38 ms      *          *                  China, Hong Kong, Telecom/CTGNet
2.49 ms      *          *                  China, Hong Kong, Telecom/CTGNet
6.17 ms      *          [CTG-CN]           China, Guangdong, Guangzhou, CTGNet
7.44 ms      *          [CN2-BackBone]     China, Guangdong, Guangzhou, chinatelecom.cn  Telecom
10.30 ms     *          [CN2-BackBone]     China, Guangdong, Guangzhou, chinatelecom.cn  Telecom
14.25 ms     *          [CN2-BackBone]     China, Guangdong, Guangzhou, chinatelecom.cn  Telecom
10.63 ms     AS4134     *                  China, Guangdong, Foshan City, chinatelecom.com.cn  Telecom
*
Guangzhou Unicom - ICMP v4 - traceroute to 210.21.196.6, 30 hops max, 52 byte packets
0.46 ms      AS152918   *                  China, Hong Kong, cdn.liberally.network 
1.11 ms      *          *                  *
0.73 ms      *          *                  *
1.29 ms      *          *                  *
12.67 ms     AS24429    *                  China, Hong Kong, alibabacloud.com 
2.30 ms      *          [CUG-ASIA]         China, Hong Kong
2.70 ms      AS10099    [CUG-BACKBONE]     China, Hong Kong, chinaunicomglobal.com  Unicom
2.76 ms      AS10099    [CUG-BACKBONE]     China, Hong Kong, chinaunicomglobal.com  Unicom
*
6.78 ms      AS4837     [CU169-BACKBONE]   China, Guangdong, Guangzhou, chinaunicom.cn  Unicom
*
12.93 ms     AS17623    [APNIC-AP]         China, Guangdong, Shenzhen, chinaunicom.cn  Unicom
10.20 ms     AS17623    *                  China, Guangdong, Shenzhen, chinaunicom.cn  Unicom
Guangzhou Mobile - ICMP v4 - traceroute to 120.196.165.24, 30 hops max, 52 byte packets
1.04 ms      AS152918   *                  China, Hong Kong, cdn.liberally.network 
*
1.75 ms      AS58807    [CMIN2-NET]        China, Hong Kong, cmi.chinamobile.com 
*
5.52 ms      AS58807    [CMIN2-NET]        China, Hong Kong, cmi.chinamobile.com  Mobile
5.12 ms      AS58807    [CMIN2-NET]        China, Guangdong, Guangzhou, cmi.chinamobile.com  Mobile
5.17 ms      AS9808     [CMNET]            China, Guangdong, Guangzhou, chinamobileltd.com  Mobile
5.04 ms      AS9808     [CMNET]            China, Guangdong, Guangzhou, chinamobileltd.com  Mobile
18.04 ms     AS9808     [CMNET]            China, Guangdong, Guangzhou, chinamobileltd.com  Mobile
11.82 ms     AS9808     [CMNET]            China, Guangdong, Guangzhou, chinamobileltd.com  Mobile
13.19 ms     AS9808     [CMNET]            China, Guangdong, Guangzhou, chinamobileltd.com  Mobile
11.42 ms     AS56040    [APNIC-AP]         China, Guangdong, Shenzhen, gd.10086.cn  Mobile

3. Mainland Three-Network Outbound Route Tests (itdog.cn, 2025-12-11）

Outbound uses each network's own backbone direct route: China Telecom 163, China Unicom 4837->10099, and China Mobile CMI.

Location	China Telecom	China Unicom	China Mobile
Beijing
Shanghai
Guangzhou

4. mainland ChinaThree-Network TCP Ping（itdog.cn, 2025-12-11 23:00）

During the evening peak, outbound routes for all three networks are fairly rough, especially China Telecom, with double-digit packet loss in many regions.

China Telecom	China Unicom	China Mobile

5. Evening Peak Direct Single-Thread Speed Tests(2025-12-06 21:40-23:00)

China Telecom starts slowly and may cut out; TLS latency is high and HTTP latency is abnormally high. Some nodes can reach speed, but others cannot.
China Unicom seems a bit better and can reach speed, but HTTP latency is still very high.
China Mobile cannot really reach speed, and latency is also high.

*Click the test record links to view speed-test screenshots, including several popular models as references.

Telecom

[Telecom Speed Test Record]

Unicom

[Unicom Speed Test Record]

Mobile

[Mobile Speed Test Record]

6. International Connectivity - iPerf3 TCP IPv4 Single-Thread Speed Test (single 10-second run, 2025-12-11)

Test Tool: iPerf3

Speed and latency within Hong Kong and across Asia-Pacific have no real issues; quite good.

[Test Record]

7. Summary

How to put it: evening-peak direct connectivity is better than unoptimized GreenCloud, but it also has clear flaws. Small-packet latency is acceptable, but HTTP latency is extremely high. I am not sure whether this is due to the China route; if not, using a landing node might help, though that would waste the native IP. Outbound routes are also quite rough. In this test, most mainland China Telecom and China Unicom nodes still had speed, but China Mobile did not perform well.

International connectivity has no real issues and is fine.

At this price (45 USD), there are other options for direct Asia-Pacific connectivity, but considering it is in Hong Kong, it depends on your needs.

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