I bought a HostHatch Seoul preorder plan on Black Friday, and it was provisioned the day before yesterday, so let's see how it performs. 
Contents
1. Configuration
2. Node Quality
3. Mainland Three-Network TCP Ping
4. Evening Peak Direct Single-Thread Speed Tests
5. International Connectivity
6. Summary
1. Configuration
| Plan | HostHatch BF25 - NVMe 4 GB - SEL |
|---|---|
| Location | Korea, Seoul |
| CPU | 2 x AMD EPYC 7763 vCores |
| RAM | 4GB |
| Disk | 50GB |
| Traffic | 1.5TB(in+out) |
| Route | international route with no mainland China optimization |
| Network | 1 x IPv4, 1 x /64 IPv6 |
| Price | Annual USD$35.00 |
Provider website: https://hosthatch.com
🔗 Quick Links
| YABS | Node Quality | Mixed Benchmark | nws.sh | Streaming Unlock |
|---|---|---|---|---|
| [Link] | [Link1] [Link2] | [Link] | [Link] | [Link] |
The upstream connects to MOACK. In the preorder provisioning email, HostHatch said that over the next few days they would add new carriers and optimize network connectivity (Over the next few days, we will be adding new carriers and optimizing connectivity.)
| IPv4 | IPv6 |
|---|---|
2. Node Quality
bash <(curl -sL https://run.NodeQuality.com)
💻 Basic Information
Performance is good.
Basic System Information:
---------------------------------
Uptime : 1 days, 6 hours, 16 minutes
Processor : AMD EPYC 7763 64-Core Processor
CPU cores : 2 @ 2449.998 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 3.8 GiB
Swap : 0.0 KiB
Disk : 46.6 GiB
Distro : Debian GNU/Linux 12 (bookworm)
Kernel : 6.12.57+deb13-cloud-amd64
VM Type : KVM
IPv4/IPv6 : ✔ Online / ✔ Online
IPv6 Network Information:
---------------------------------
ISP : HostHatch
ASN : Unknown
Host : HostHatch, Inc
Location : Tampa, Florida (FL)
Country : United States
fio Disk Speed Tests (Mixed R/W 50/50) (Partition -):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 152.04 MB/s (38.0k) | 1.72 GB/s (27.0k)
Write | 152.44 MB/s (38.1k) | 1.73 GB/s (27.1k)
Total | 304.48 MB/s (76.1k) | 3.46 GB/s (54.1k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 4.64 GB/s (9.0k) | 4.77 GB/s (4.6k)
Write | 4.88 GB/s (9.5k) | 5.09 GB/s (4.9k)
Total | 9.53 GB/s (18.6k) | 9.86 GB/s (9.6k)
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 1132
Multi Core | 2216
Full Test | https://browser.geekbench.com/v5/cpu/23976567
SysBench CPU Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
1 Thread Test (Single Core) Score: 3470 Scores
2 Thread Test (Multi Core) Score: 6931 Scores
SysBench Memory Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
Single-Thread Read Test: 43173.07 MB/s
Single-Thread Write Test: 25382.72 MB/s
🎬IP Quality
Anycast/broadcast IP; geolocation is not very accurate yet.
| IPv4 | IPv6 |
|---|---|
🌐 Network Quality
| IPv4 | IPv6 |
|---|---|
📍Return Routes
LG UPLUS route, with direct backbone connectivity for all three mainland networks.
| IPv4 | IPv6 |
|---|---|
3. mainland ChinaThree-Network TCP Ping(itdog.cn, 2025-12-16 22:00)
Evening-peak latency is fairly high and jitter is severe, but packet loss is acceptable.
| China Telecom | China Unicom | China Mobile |
|---|---|---|
4. Evening Peak Direct Single-Thread Speed Tests(2025-12-16 21:00-23:00)
During the evening peak, China Telecom and China Mobile have almost no speed; China Unicom can still run a bit, though with higher latency.
Telecom
| Node | Average Speed | Maximum Speed | Latency RTT | HTTP Latency |
|---|---|---|---|---|
| ShanghaiTelecom@1Gbps | 7.22Mbps | 10.99Mbps | 156ms | 883ms |
| Ningbo, ZhejiangTelecom@2Gbps | 6.58Mbps | 8.72Mbps | 229ms | 1080ms |
| Xi'an Telecom@2Gbps | 38.53Mbps | 63.83Mbps | 224ms | 719ms |
| Xi'an Telecom@1Gbps | 34.16Mbps | 89.95Mbps | 160ms | 884ms |
| ShenzhenTelecom@1Gbps | 44.27Mbps | 91.87Mbps | 135ms | 904ms |
| GuangdongTelecom@1Gbps | 5.64Mbps | 9.63Mbps | 119ms | 986ms |
| Eastern Guangdong Telecom@1Gbps | 131.97Mbps | 195.43Mbps | 252ms | 1402ms |
| GuangxiTelecom@1Gbps | 18.55Mbps | 81.33Mbps | 227ms | 1129ms |
Unicom
| Node | Average Speed | Maximum Speed | Latency RTT | HTTP Latency |
|---|---|---|---|---|
| ShanghaiUnicom@1Gbps | 104.75Mbps | 732.70Mbps | 137ms | 535ms |
| ShaoxingUnicom@1Gbps | 205.99Mbps | 266.60Mbps | 259ms | 580ms |
| ShandongUnicom@1Gbps | 32.77Kbps | 262.14Kbps | 539ms | 1909ms |
| ShanxiUnicom@1Gbps | 507.85Mbps | 617.04Mbps | 226ms | 511ms |
| LiaoningUnicom@1Gbps | 140.02Mbps | 197.01Mbps | 138ms | 586ms |
| GuangdongUnicom@1Gbps | 56.62Mbps | 150.81Mbps | 275ms | 583ms |
| WuhanUnicom@2.5Gbps | 0bps | 0bps | 196ms | 645ms |
Mobile
| Node | Average Speed | Maximum Speed | Latency RTT | HTTP Latency |
|---|---|---|---|---|
| Shanghai Mobile@2Gbps | 1.98Mbps | 2.62Mbps | 235ms | 1097ms |
| Lishui Mobile@1Gbps | 79.70Mbps | 129.80Mbps | 215ms | 1088ms |
| Hebei Mobile@1Gbps | 38.34Kbps | 43.85Kbps | 248ms | 880ms |
| Northeast China Mobile@1Gbps | 10.94Kbps | 43.82Kbps | 507ms | 1523ms |
| Shanxi Mobile@1Gbps | 401.41Kbps | 1.57Mbps | 294ms | 1041ms |
| Guangzhou Mobile@1Gbps | 483.23Kbps | 1.11Mbps | 381ms | 1423ms |
| Guangxi Mobile@1Gbps | 6.03Mbps | 9.09Mbps | 251ms | 1091ms |
| Sichuan Mobile@1Gbps | 241.32Kbps | 655.17Kbps | 277ms | 1686ms |
Premium Network
Shanghai Telecom CN2 is quite good.
| Node | Average Speed | Maximum Speed | Latency RTT | HTTP Latency |
|---|---|---|---|---|
| ShanghaiTelecomCN2@2.5Gbps | 405.82Mbps | 735.53Mbps | 60ms | 309ms |
| ShanghaiUnicom9929@2.5Gbps | 53.58Mbps | 387.74Mbps | 302ms | 995ms |
| BeijingUnicom9929@2.5Gbps | 52.16Mbps | 376.68Mbps | 274ms | 962ms |
[Premium NetworkSpeed Test Record]
5. International Connectivity
Looking at web latency, many sites route through Japan, probably because many websites have no CDN nodes in Korea but do have them in Japan.
HostHatch has plenty of local bandwidth; it saturated the Seoul Lightnode port, and performance to Hong Kong and Japan is also good, though latency still needs optimization.
Web Latency
bash <(wget -qO- https://raw.githubusercontent.com/danger-dream/network-latency-tester/main/latency.sh)
Latency Test(ping.pe)
| IPv4 | IPv6 |
|---|---|
Speed Test - iPerf3 TCP IPv4 Single-Thread (single 10-second run, 2025-12-15)
Test Tool: iPerf3
| Region | Node | Average/Max Upload (Mbps) | Average/Max Download (Mbps) | Latency (ms) |
|---|---|---|---|---|
| 🇰🇷 Seoul | AWS Lightsail | 4042 / 4165 | 4715 / 4776 | 3.55 |
| 🇯🇵 Tokyo | DMIT T1 | 2771 / 2986 | 3175 / 3497 | 33.87 |
| 🇯🇵 Tokyo | BAGE JP | 3755 / 4042 | 3677 / 3991 | 31.53 |
| 🇯🇵 Tokyo | BAGE JPS | 4335 / 4613 | 4340 / 4773 | 31.72 |
| 🇯🇵 Tokyo | Nube | 3973 / 4246 | 2638 / 3001 | 32.41 |
| 🇯🇵 Tokyo | GreenCloud SB | 3634 / 4095 | 5048 / 5276 | 34.31 |
| 🇯🇵 Tokyo | GreenCloud IIJ | 843 / 2300 | 1039 / 1464 | 60.73 |
| 🇯🇵 Tokyo | DDPS CDN77 | 3608 / 4189 | 5284 / 5562 | 32.14 |
| 🇯🇵 Tokyo | RFCHOST T1 | 4695 / 4969 | 4367 / 4858 | 37.42 |
| 🇯🇵 Tokyo | YxVM VOL | 5442 / 5803 | 4979 / 5233 | 34.39 |
| 🇯🇵 Tokyo | NNC STD | 4685 / 5313 | 5405 / 5609 | 31.81 |
| 🇯🇵 Tokyo | FxTransit | 131 / 176 | 4722 / 5070 | 32.63 |
| 🇯🇵 Tokyo | SkylineConnect | 4715 / 5055 | 4017 / 4337 | 35.41 |
| 🇭🇰 Hong Kong | DMIT T1 | 1326 / 3022 | 2786 / 2984 | 55.35 |
| 🇭🇰 Hong Kong | RFCHOST JINX | 1194 / 2088 | 2742 / 2956 | 61.36 |
| 🇭🇰 Hong Kong | RFCHOST CTC | 2601 / 2850 | 2785 / 2980 | 60.72 |
| 🇭🇰 Hong Kong | Nube | 2332 / 2520 | 2474 / 2640 | 59.64 |
| 🇭🇰 Hong Kong | GreenCloud DC1 | 3042 / 3285 | 3002 / 3196 | 59.45 |
| 🇭🇰 Hong Kong | GreenCloud DC2 | 4448 / 4792 | 4259 / 4549 | 36.46 |
| 🇭🇰 Hong Kong | HostHatch | 2933 / 3209 | 2961 / 3151 | 59.81 |
| 🇭🇰 Hong Kong | YxVM VOL | 4555 / 4868 | 4454 / 4704 | 37.43 |
| 🇭🇰 Hong Kong | FxTransit | 2917 / 3351 | 3014 / 3206 | 60.17 |
| 🇭🇰 Hong Kong | Hytron | 2574 / 2973 | 2684 / 2875 | 60.77 |
| 🇭🇰 Hong Kong | Halo STD | 2782 / 3034 | 2815 / 3061 | 59.99 |
| 🇭🇰 Hong Kong | Halo Lite | 2785 / 2995 | 2567 / 2807 | 57.43 |
| 🇭🇰 Hong Kong | BAGE HKS | 990 / 1042 | 1010 / 1070 | 37.17 |
| 🇭🇰 Hong Kong | BAGE HKL | 964 / 1049 | 887 / 996 | 55.55 |
| 🇭🇰 Hong Kong | ClawCloud | 440 / 731 | 1031 / 1052 | 37.90 |
| 🇭🇰 Hong Kong | Servps | 841 / 951 | 1041 / 1495 | 58.69 |
| 🇭🇰 Hong Kong | Boil HKT | 555 / 728 | 472 / 621 | 215.33 |
| 🇭🇰 Hong Kong | Kaze HKBN | 1560 / 1866 | 1136 / 1220 | 67.57 |
| 🇸🇬 Singapore | RFCHOST T1 | 2033 / 2247 | 1996 / 2179 | 79.93 |
| 🇸🇬 Singapore | BAGE SG | 1917 / 2149 | 1980 / 2164 | 82.46 |
| 🇸🇬 Singapore | BAGE SGS | 1969 / 2164 | 2000 / 2183 | 81.05 |
| 🇸🇬 Singapore | GreenCloud DC1 | 2460 / 2657 | 2436 / 2638 | 67.97 |
| 🇸🇬 Singapore | GreenCloud DC2 | 2063 / 2342 | 956 / 1180 | 75.98 |
| 🇸🇬 Singapore | Nube | 957 / 1195 | 1960 / 2174 | 82.05 |
| 🇸🇬 Singapore | SkylineConnect | 1742 / 1950 | 1960 / 2140 | ERR |
| 🇸🇬 Singapore | IDC.Care | 871 / 1014 | 847 / 1041 | 73.61 |
| 🇻🇳 Hanoi | GreenCloud | 2076 / 2325 | 1281 / 1391 | 77.81 |
| 🇻🇳 Ho Chi Minh City | GreenCloud | 1271 / 1583 | 1298 / 1737 | 100.83 |
| 🇮🇳 Mumbai | HostDZire | 246 / 362 | 365 / 473 | 144.43 |
| 🇦🇺 Sydney | GreenCloud | 978 / 1182 | 496 / 576 | 158.75 |
| 🇺🇸 Los Angeles | DMIT T1 | 847 / 1006 | 1173 / 1362 | 129.25 |
| 🇺🇸 Los Angeles | GreenCloud | 911 / 1094 | 777 / 924 | 163.44 |
| 🇺🇸 Los Angeles | AlphaVPS | 917 / 1135 | 907 / 1087 | 161.95 |
| 🇺🇸 Los Angeles | HostDZire | 890 / 1087 | 881 / 1064 | 161.78 |
| 🇺🇸 Los Angeles | BAGE LA1 | 849 / 1081 | 642 / 994 | 164.18 |
| 🇺🇸 Los Angeles | BAGE LA2 | 781 / 995 | 575 / 773 | 137.95 |
| 🇺🇸 Los Angeles | RFCHOST T1 | 780 / 911 | 567 / 844 | 145.05 |
| 🇺🇸 San Jose | HostDZire | 945 / 1180 | 939 / 1122 | 159.47 |
| 🇺🇸 San Jose | GreenCloud | 249 / 490 | 562 / 742 | 239.82 |
| 🇺🇸 San Jose | Nube | 739 / 903 | 802 / 974 | 162.49 |
| 🇺🇸 Las Vegas | BuyVM | 888 / 1270 | 1008 / 1187 | 144.04 |
| 🇺🇸 Seattle | Misaka | 1136 / 1367 | 1129 / 1313 | 135.09 |
| 🇺🇸 Seattle | AlphaVPS | 1337 / 1561 | 1367 / 1570 | 114.86 |
| 🇺🇸 Ogden | GreenCloud | 999 / 1203 | 442 / 624 | 151.32 |
| 🇺🇸 Salt Lake City | BAGE | 870 / 1045 | 741 / 860 | 143.36 |
| 🇺🇸 Dallas | AlphaVPS | 719 / 908 | 726 / 905 | 200.08 |
| 🇺🇸 Jacksonville | GreenCloud | 634 / 812 | 633 / 817 | 219.12 |
| 🇺🇸 Chicago | GreenCloud DC1 | 672 / 898 | 711 / 890 | 199.97 |
| 🇺🇸 Chicago | GreenCloud DC2 | 739 / 993 | 700 / 880 | 198.07 |
| 🇺🇸 Ashburn | GreenCloud | 538 / 773 | 700 / 890 | 206.17 |
| 🇺🇸 Washington | HostDZire | 688 / 904 | 292 / 452 | 206.23 |
| 🇺🇸 New York | AlphaVPS | 623 / 807 | 694 / 875 | 206.53 |
| 🇩🇪 Frankfurt | BAGE | 595 / 811 | 260 / 436 | 228.86 |
| 🇩🇪 Frankfurt | GreenCloud | 472 / 730 | 503 / 684 | 259.39 |
| 🇩🇪 Frankfurt | Nube | 622 / 830 | 276 / 535 | 221.06 |
| 🇩🇪 Frankfurt | BERO | 440 / 628 | 440 / 620 | 282.07 |
| 🇩🇪 Nuremberg | Netcup | 501 / 720 | 158 / 357 | 254.96 |
| 🇩🇪 Nuremberg | AlphaVPS | 401 / 809 | 196 / 359 | 223.83 |
| 🇳🇱 Amsterdam | GreenCloud | 417 / 548 | 518 / 699 | 258.92 |
| 🇨🇭 Zurich | Aluy | 428 / 626 | 467 / 663 | 261.25 |
| 🇧🇬 Sofia | AlphaVPS | 370 / 729 | 233 / 391 | 252.77 |
| 🇬🇧 London | AlphaVPS | 684 / 904 | 621 / 792 | 206.10 |
| 🇬🇧 Coventry | BAGE | 235 / 407 | 275 / 462 | 238.83 |
| 🇬🇧 Coventry | GreenCloud | 602 / 811 | 581 / 763 | 228.32 |
6. Summary
Performance is fairly good and it suits websites aimed at Japan and Korea, but it is not very suitable for proxy use. Although the route back to China is LG UPLUS, evening-peak direct speed still cannot climb. At the same time, accessing many overseas sites from Korea, especially global services, often requires detouring through Japan, adding more than 30 ms of latency. For pure proxy use, if you do not strictly need a Korea landing node, a Japan landing node is better; Japan has more mature direct optimized routes and dedicated-line resources, with more choices.
7. 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
8. Acknowledgements
Thanks to "Impart Speed Test“(@Kyoma ) for providing the mainland Chinapublic-interest speed test service