I bought a QDE Black Friday flash-sale plan to see how it performs. 
Contents
1. Configuration
2. Node Quality
3. Streaming unlock
4. itdog test
5. International connectivity
6. Summary
1. Configuration
| Plan | 🇳🇱 QDE Budget VPS BF 2025 |
|---|---|
| Location | Netherlands, Amsterdam |
| CPU | 2 x Intel E5-2690v4 vCPU |
| RAM | 1GB |
| Disk | 15GB |
| Traffic | 2TB(in+out) |
| Route | international route with no Mainland China optimization |
| Bandwidth | 1Gbps |
| Network | 1 x IPv4, 1 x /64 IPv6 |
| Price | annually EUR€9.95 (CNY¥81.64) |
Provider website: https://qde.com
🔗 Quick links
| YABS | Node Quality | nws.sh | Streaming unlock |
|---|---|---|---|
| [Link] | [Link] | [Link] | [Link] |
upstreamxTom
2. Node Quality
bash <(curl -sL https://run.NodeQuality.com)
💻Basic information
Performance is actually fine; it comes with two cores.
Basic System Information:
---------------------------------
Uptime : 0 days, 3 hours, 8 minutes
Processor : Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz
CPU cores : 2 @ 2599.996 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 929.7 MiB
Swap : 571.0 MiB
Disk : 16.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 : Hizakura B.V.
ASN : AS210429 Hizakura B.V.
Host : Hizakura B.V
Location : Amsterdam, North Holland (NH)
Country : Netherlands
fio Disk Speed Tests (Mixed R/W 50/50) (Partition -):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 228.27 MB/s (57.0k) | 1.43 GB/s (22.4k)
Write | 228.87 MB/s (57.2k) | 1.44 GB/s (22.5k)
Total | 457.14 MB/s (114.2k) | 2.87 GB/s (44.9k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 1.89 GB/s (3.6k) | 1.86 GB/s (1.8k)
Write | 1.99 GB/s (3.8k) | 1.98 GB/s (1.9k)
Total | 3.88 GB/s (7.5k) | 3.84 GB/s (3.7k)
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 768
Multi Core | 1497
Full Test | https://browser.geekbench.com/v5/cpu/23939497
SysBench CPU Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
1 Thread Test (Single Core) Score: 989 Scores
2 Thread Test (Multi-Core) Score: 1945 Scores
SysBench Memory Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
Single-thread Read Test: 19996.19 MB/s
Single-thread Write Test: 14849.04 MB/s
🎬IP quality
Native IP, good unlocking.
| IPv4 | IPv6 |
|---|---|
🌐Network quality
| IPv4 | IPv6 |
|---|---|
📍Return route
| IPv4 | IPv6 |
|---|---|
3. Streaming unlock
bash <(curl -L -s check.unlock.media)
| IPv4 | IPv6 |
|---|---|
4. TCP PING(itdog.cn,2025-11-30 22:00)
During evening peak, as measured by the NQ script, direct-connection latency is very high, but the packet-loss rate is not high. Unicom jitter is much lower than the other two major carriers.
| China Telecom | China Unicom | China Mobile |
|---|---|---|
5. International connectivity
Europe route-machine speed tests
Upload corresponds to return-route speed. BandwagonHost return speed seems average, testing below 500Mbps, which naturally affects mainland return speed when wrapped through a landing node. SaltyFish has no such issue.
| Region | Node | Average/max upload (Mbps) | Average/max download (Mbps) | Latency (ms) |
|---|---|---|---|---|
| 🇳🇱 Amsterdam | BandwagonHOST | 448 / 469 | 2122 / 2160 | 1.93 |
| 🇳🇱 Amsterdam | SaltyFish PRE | 1159 / 1866 | 2131 / 2200 | 1.39 |
| 🇩🇪 Frankfurt | SaltyFish PRE | 1159 / 2268 | 2112 / 2211 | 7.59 |
| 🇷🇺 Moscow | Misaka w/ CN2 | 1123 / 1588 | 1123 / 1588 | 43.99 |
International speed tests
Upload can reach 1G, which is good; pulling from Hong Kong may have relatively high latency.
Some nodes are not shown; see the full version at image host
| Region | Node | Average/max upload (Mbps) | Average/max download (Mbps) | Latency (ms) |
|---|---|---|---|---|
| 🇳🇱 Amsterdam | GreenCloud | 1136 / 2101 | 2214 / 2243 | 0.58 |
| 🇬🇧 London | AlphaVPS | 1161 / 2239 | 2102 / 2154 | 7.16 |
| 🇬🇧 Coventry | BAGE | 780 / 835 | 754 / 818 | 11.34 |
| 🇬🇧 Coventry | GreenCloud | 1163 / 2232 | 2041 / 2199 | 10.55 |
| 🇩🇪 Frankfurt | BAGE | 1094 / 1341 | 471 / 508 | 15.16 |
| 🇩🇪 Frankfurt | GreenCloud | 959 / 1194 | 477 / 545 | 15.78 |
| 🇩🇪 Frankfurt | Nube | 1168 / 2272 | 2101 / 2254 | 11.32 |
| 🇩🇪 Frankfurt | BERO | 1148 / 2136 | 2145 / 2188 | 7.01 |
| 🇩🇪 Nuremberg | Netcup | 925 / 976 | 412 / 445 | 10.34 |
| 🇩🇪 Nuremberg | AlphaVPS | 488 / 548 | 469 / 530 | 15.97 |
| 🇨🇭 Zurich | Aluy | 1146 / 2047 | 476 / 547 | 18.75 |
| 🇧🇬 Sofia | AlphaVPS | 708 / 830 | 862 / 902 | 32.04 |
| 🇭🇰 Hong Kong | DMIT T1 | 781 / 1019 | 377 / 699 | 182.02 |
| 🇭🇰 Hong Kong | RFCHOST JINX | 837 / 1046 | 726 / 942 | 173.00 |
| 🇭🇰 Hong Kong | RFCHOST CTC | 856 / 1042 | 777 / 960 | 169.58 |
| 🇭🇰 Hong Kong | Nube | 404 / 545 | 567 / 761 | 234.95 |
| 🇭🇰 Hong Kong | GreenCloud DC1 | 816 / 1045 | 467 / 900 | 185.51 |
| 🇭🇰 Hong Kong | GreenCloud DC2 | 551 / 852 | 270 / 393 | 192.12 |
| 🇭🇰 Hong Kong | HostHatch | 778 / 1025 | 786 / 968 | 185.79 |
| 🇭🇰 Hong Kong | YxVM VOL | 714 / 930 | 792 / 978 | 182.88 |
| 🇭🇰 Hong Kong | FxTransit | 505 / 867 | 266 / 420 | 205.49 |
| 🇭🇰 Hong Kong | Hytron | 121 / 238 | 244 / 502 | 306.55 |
| 🇭🇰 Hong Kong | Halo STD | 826 / 1039 | 187 / 346 | 199.09 |
| 🇭🇰 Hong Kong | Halo Lite | 535 / 763 | 242 / 341 | 233.57 |
| 🇭🇰 Hong Kong | BAGE HKS | 175 / 323 | 97 / 121 | 160.09 |
| 🇭🇰 Hong Kong | BAGE HKL | 354 / 534 | 647 / 922 | 194.26 |
| 🇭🇰 Hong Kong | ClawCloud | 608 / 827 | 268 / 474 | 208.00 |
| 🇭🇰 Hong Kong | Servps | 306 / 389 | 205 / 349 | 197.04 |
| 🇭🇰 Hong Kong | Boil HKT | 409 / 648 | 548 / 679 | 195.90 |
| 🇭🇰 Hong Kong | Kaze HKBN | 501 / 714 | 211 / 345 | 198.47 |
| 🇯🇵 Tokyo | DMIT T1 | 675 / 895 | 672 / 858 | 208.49 |
| 🇯🇵 Tokyo | BAGE JP | 608 / 832 | 668 / 856 | 208.66 |
| 🇯🇵 Tokyo | BAGE JPS | 677 / 927 | 674 / 858 | 208.66 |
| 🇯🇵 Tokyo | GreenCloud SB | 488 / 823 | 283 / 517 | 224.60 |
| 🇯🇵 Tokyo | GreenCloud IIJ | 335 / 647 | 475 / 798 | 233.74 |
| 🇯🇵 Tokyo | RFCHOST T1 | 634 / 841 | 214 / 328 | 216.42 |
| 🇯🇵 Tokyo | YxVM VOL | 630 / 837 | 295 / 538 | 225.93 |
| 🇯🇵 Tokyo | FxTransit | 120 / 185 | 573 / 822 | 224.01 |
| 🇸🇬 Singapore | RFCHOST T1 | 945 / 1132 | 888 / 1110 | 159.88 |
| 🇸🇬 Singapore | BAGE SG | 956 / 1219 | 967 / 1158 | 154.42 |
| 🇸🇬 Singapore | BAGE SGS | 653 / 839 | 272 / 460 | 216.00 |
| 🇸🇬 Singapore | GreenCloud DC1 | 953 / 1228 | 393 / 569 | 152.65 |
| 🇸🇬 Singapore | GreenCloud DC2 | 505 / 734 | 292 / 467 | 243.81 |
| 🇺🇸 Los Angeles | DMIT T1 | 675 / 844 | 335 / 440 | 138.52 |
| 🇺🇸 Los Angeles | GreenCloud | 1001 / 1324 | 1037 / 1289 | 138.25 |
| 🇺🇸 San Jose | GreenCloud | 1014 / 1330 | 359 / 520 | 138.38 |
| 🇺🇸 San Jose | Nube | 841 / 1024 | 322 / 428 | 142.19 |
| 🇺🇸 Seattle | Misaka | 980 / 1231 | 388 / 559 | 154.15 |
| 🇺🇸 Ogden | GreenCloud | 1039 / 1447 | 1181 / 1491 | 119.51 |
| 🇺🇸 New York | AlphaVPS | 1071 / 1973 | 1580 / 1883 | 74.92 |
Mainland premium-network speed tests
Beijing 9929 direct connection is still good.
| Region | Node | Average/max upload (Mbps) | Average/max download (Mbps) | Latency (ms) |
|---|---|---|---|---|
| 🇨🇳 Beijing | CoolSnow 9929 | 397 / 505 | 59 / 261 | 140.24 |
| 🇨🇳 Shanghai | Liqun CN2 | 233 / 338 | 4 / 16 | 223.86 |
| 🇨🇳 Shanghai | Liqun 9929 | 246 / 303 | 18 / 105 | 192.50 |
Hong Kong-Europe routes
DMIT is using GSL to Europe again. Although the three CTC-series machines all use RETN outbound, this time only BAGE HKS uses RETN return to Hong Kong, and its latency is clearly lower than the other two, though speed did not get going. YxVM uses RETN return but detours via Singapore. Halo (Akari) does not use RETN at all.
| 🇭🇰 DMIT <-> 🇳🇱 QDE | 🇭🇰 RFCHOST JINX <-> 🇳🇱 QDE | 🇭🇰 BAGE HKS <-> 🇳🇱 QDE | 🇭🇰 YxVM <-> 🇳🇱 QDE | 🇭🇰 Halo STD <-> 🇳🇱 QDE |
|---|---|---|---|---|
| Outbound | Outbound | Outbound | Outbound | Outbound |
| Return | Return | Return | Return | Return |
6. Summary
A pretty good Europe landing-node machine. It is best paired with a Europe route machine or Beijing 9929. If you care about latency, I do not recommend direct connection. Pulling directly from Hong Kong has speed, but latency measured this time is a bit high.
7. 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