VMISS.COM .JP.TKY.TRI.Basic
I recently took a look at VMISS’s Tokyo TRI lineup. This thing is basically impossible to grab manually when it comes back in stock, so I ended up paying around 30 RMB over retail to get one from someone else.
The JP.TKY.TRI.Basic is a pretty straightforward little VPS. The specs aren’t impressive, the traffic allowance isn’t huge, and the port is capped at just 100Mbps. The real selling point here is the network.
It’s definitely not something I’d buy specifically for hosting a website, although technically, you absolutely can.
Specs
CPU: 1 Core
RAM: 1GB
Storage: 10GB SSD
Port: 100Mbps
Traffic: 400GB/month
IPv4: 1
Location: Tokyo, Japan
Network: TRI China-optimized routing
Price: Around 10 CAD/month
There’s really nothing exciting about the hardware. 1C1G with a 10GB SSD is about as basic as a small VPS gets.
What makes this VPS interesting is the connectivity back to mainland China.
Pros: China Telecom, China Unicom and China Mobile optimized routes, Tokyo location, and relatively low latency to mainland China.
Cons: Only a 100Mbps port and just 400GB of monthly traffic.
NodeQuality Full Test
######################################################################## bash <(curl -sL https://run.NodeQuality.com) https://github.com/LloydAsp/NodeQuality Test Time: 2026-09-16 11:45:58 CST Script Version: v0.0.1 Channel: https://t.me/nodeselect Website: https://NodeQuality.com ######################################################################## ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Hardware Quality Test: 64.83.*.* https://github.com/xykt/HardwareQuality bash <(curl -sL https://Check.Place) -H Test Time: 2026-09-16 11:46:14 CST Script Version: v2026-05-21 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1. Operating System Virtualization: KVM Architecture: x86_64 OS / Kernel: Debian GNU/Linux 12 (bookworm) 6.8.0-90-generic Uptime: 30 days 17 hours 10 minutes Load Average: 0.47, 0.11, 0.04 Processes: 3 users, 105 processes, 22/237 active/total services Locale: C, UTF-8, Etc/UTC UTC +0000 2. Motherboard / Virtual Hardware BIOS: SeaBIOS, version 1.16.0-1.module_el8.7.0+1140+ff0772f9 Chipset: Intel 82371SB PIIX3 ISA [Natoma/Triton II] Intel 440FX - 82441FX PMC [Natoma] NIC: Red Hat, Inc. Virtio network device 3. CPU Benchmark CPU: AMD EPYC-Milan Processor Stepping 1 (25th Gen) 32/64-bit ╚═ 1 Core, 1 Thread, 2645.030MHz, 5% utilization Cache: L1d 32 KiB, L1i 32 KiB, L2 512 KiB, L3 32 MiB Instruction Sets: ✘ VT-x/AMD-V ✔ AES-NI ✔ AVX2 ✔ BMI1/2 ✘ EPT/NPT Sysbench Single Thread: 3680.70 GB5 Reference: J1900 N5105 N100 6700K 9900K 5900X 12900K 14900K 7713 7995WX GB5 Single Core: |1079 GB5 Multi Core: |1031 Full Result: https://browser.geekbench.com/v5/cpu/24635874 5. Memory Benchmark RAM: 962 MB total, 366 MB used (38%), 596 MB available (62%) Overselling Indicators: ✘ Ballooning ✘ KSM Sysbench: Read 47138.3 MB/s, Write 28258.7 MB/s, Latency 158 ns 6. Disk Benchmark Disk: 1 drive, 8.7GB total, 4.3GB used (48%), 4.5GB available (52%) Test Device: vda1(/r**t) -> DISK Fio: RND4K/Q1 IOPS || RND4K/Q32 IOPS || SEQ1M/Q1 IOPS || SEQ1M/Q8 IOPS Read: 56.2MB/s 14k || 335MB/s 86k || 2698MB/s 2.7k || 13866MB/s 14k Write: 50.2MB/s 13k || 218MB/s 56k || 1850MB/s 1.9k || 3246MB/s 3.2k 7. Hardware Quality Score Category: Total / CPU / GPU / RAM / Disk Score: 28182 = 14681 + N/A + 11731 + 1770 Ranking: 5.2% / 9.4% / N/A / 6.8% / 4.6% ================================================================================ Hardware Report: https://Report.Check.Place/hardware/YYP17U3AL.svg
IP Quality
######################################################################## IP Quality Test: 64.83.*.* https://github.com/xykt/IPQuality bash <(curl -sL https://Check.Place) -I Test Time: 2026-09-16 11:50:02 CST Script Version: v2026-09-16 ######################################################################## 1. Basic Information (MaxMind) ASN: AS979 Organization: NetLab Global Location: [JP] Japan Registered in: [HK] Hong Kong IP Type: Anycast IP 2. IP Type Database: IPinfo / ipregistry / ipapi / IP2Location / AbuseIPDB Usage Type: Business / Business / Datacenter / Datacenter / Business Company Type: Business / Datacenter / Residential / Datacenter 3. Risk Scores IP2Location: 3 | Low Risk Scamalytics: 0 | Low Risk ipapi: 1.12% AbuseIPDB: 0 | Low Risk DB-IP: Low Risk 4. Risk Factors Database: IP2Location / ipapi / ipregistry / IPQS / Scamalytics / ipdata / IPinfo / DB-IP Region: [JP] [JP] [JP] N/A [JP] [US] [JP] [JP] Proxy: No / No / No / N/A / No / No / No / No Tor: No / No / No / N/A / No / No / No / N/A VPN: No / No / No / N/A / No / N/A / No / N/A Server: Yes / Yes / Yes / N/A / No / No / No / N/A Abuse: No / No / No / N/A / No / No / N/A / N/A Bot: No / No / N/A / N/A / No / N/A / N/A / No 5. Streaming & AI Unlock Test Service: TikTok / Disney+ / Netflix / YouTube / Amazon Prime Video / Reddit / ChatGPT Status: Unlocked / Unlocked / Unlocked / Unlocked / Unlocked / Unlocked / Unlocked Region: [JP] / [JP] / [JP] / [JP] / [JP] / [JP] / [JP] Type: Native / Native / Native / Native / Native / Native / Native 6. Mail & Blacklist Test Outbound Port 25: Blocked Remote Port 25: Unreachable Blacklist Databases: 423 checked 398 clean 25 flagged 0 blacklisted ======================================================================== IP Quality Report: https://Report.Check.Place/ip/3BZ5QI5L2.svg
Network Quality
******************************************************************************** Network Quality Test: 64.83.*.* https://github.com/xykt/NetQuality bash <(curl -sL https://Check.Place) -N Test Time: 2026-09-16 11:51:56 CST Script Version: v2026-09-01 ******************************************************************************** 1. BGP Information Registration: RIPE, NTT America, Inc. Registered / Updated: 2026-02-25 / 2026-05-24 Region: [JP] Japan, Eastern Asia, Asia 2. Local Network Settings NAT Type: Open Internet / No NAT TCP Congestion Control: BBR TCP Receive Buffer (rmem): 4096 131072 6291456 Queue Discipline: fq TCP Send Buffer (wmem): 4096 16384 4194304 3. Connectivity Internet Exchanges: - Upstreams: - Peers: - 4. China Telecom / Unicom / Mobile TCP Latency Beijing: CT 52ms | CU 51ms | CM 55ms Tianjin: CT 55ms | CU 50ms | CM 59ms Hebei: CT 55ms | CU 60ms | CM 61ms Shanxi: CT 60ms | CU 141ms | CM 70ms Shanghai: CT 31ms | CU 33ms | CM 39ms Jiangsu: CT 42ms | CU 39ms | CM 44ms Zhejiang: CT 34ms | CU 37ms | CM 37ms Fujian: CT 45ms | CU 54ms | CM 71ms Hubei: CT 42ms | CU 50ms | CM 70ms Hunan: CT 56ms | CU 53ms | CM 76ms Guangdong: CT 60ms | CU 61ms | CM 70ms Guangxi: CT 68ms | CU 40ms | CM 74ms Sichuan: CT 63ms | CU 64ms | CM 89ms Guizhou: CT 61ms | CU 65ms | CM 92ms Yunnan: CT 68ms | CU 67ms | CM 90ms Xinjiang: CT 58ms | CU 105ms | CM 96ms 5. Return Routes to Mainland China (NextTrace API) Beijing TCP: China Telecom: AS979 -> CTG GIA China Unicom: AS979 -> AS10099 China Mobile: AS979 -> CMI Beijing UDP: China Telecom: AS979 -> CTG GIA China Unicom: AS979 -> AS10099 China Mobile: AS979 -> CMI Shanghai TCP: China Telecom: AS979 -> CTG GIA China Unicom: AS979 -> AS10099 China Mobile: AS979 -> CMI Shanghai UDP: China Telecom: AS979 -> CTG GIA China Unicom: AS979 -> AS10099 China Mobile: AS979 -> CMI Guangzhou TCP: China Telecom: AS979 -> CTG GIA China Unicom: AS979 -> AS10099 China Mobile: AS979 -> CMI Guangzhou UDP: China Telecom: AS979 -> CTG GIA China Unicom: AS979 -> AS10099 China Mobile: AS979 -> CMI 6. China Speed Tests Shanghai Unicom: Upload: 1170Mbps Upload Latency: 144ms Download: 95Mbps Download Latency: 49ms Suzhou Mobile: Upload: 1173Mbps Upload Latency: 310ms Download: 1Mbps Download Latency: 364ms 7. International Connectivity Hong Kong: 262ms | Upload 72Mbps | Download 66Mbps Tokyo: 1ms | Upload 5499Mbps | Download 95Mbps Singapore: 259ms | Upload 75Mbps | Download 66Mbps Sydney: 175ms | Upload 125Mbps | Download 71Mbps Los Angeles: 157ms | Upload 146Mbps | Download 80Mbps New York: 152ms | Upload 123Mbps Frankfurt: 230ms | Upload 66Mbps | Download 56Mbps London: 235ms | Upload 75Mbps | Download 69Mbps Amsterdam: 228ms | Upload 95Mbps | Download 69Mbps São Paulo: 300ms | Upload 52Mbps | Download 39Mbps ================================================================================ Network Report: https://Report.Check.Place/net/KR8LW6CMR.svg
Detailed Return Routes to Mainland China
******************************************************************************** Network Quality Test: 64.83.*.* Test Time: 2026-09-16 11:58:18 CST ******************************************************************************** BEIJING - CHINA TELECOM AS979 -> CTG GIA Geographic Route: Japan -> Beijing ASN Path: AS979 -> AS23764 -> AS4809 -> AS4134 -> AS4847 1 0.85ms 64.83.*.* AS979 Japan, Tokyo 2 0.77ms 10.81.*.* RFC1918 4 0.42ms 69.194.*.* China Telecom 5-7 0.42ms 203.128.*.* AS23764 Tokyo, Japan China Telecom Global 8 27.91ms 203.22.*.* [CTG-CN] Tokyo, Japan 9-10 48.02ms 59.43.*.* AS4809 [CN2-BackBone] Beijing, China 11-12 60.90ms 202.97.*.* AS4134 [CHINANET-BB] Beijing, China 14 55.98ms 36.112.*.* AS4847 Beijing, China 15-16 62.25ms 219.141.*.* AS4847 Beijing, China 17 54.83ms 106.37.*.* AS4847 Beijing, China BEIJING - CHINA UNICOM AS979 -> AS10099 Geographic Route: Japan -> Shanghai -> Beijing ASN Path: AS979 -> AS10099 -> AS4837 -> AS4808 1 0.88ms 64.83.*.* AS979 Tokyo, Japan 2 0.38ms 10.81.*.* RFC1918 5-8 1.13ms 203.160.*.* AS10099 Tokyo, Japan China Unicom Global 9-11 51.58ms 219.158.*.* AS4837 Shanghai, China 14-15 57.32ms 61.148.*.* AS4808 Beijing, China 17 54.25ms 221.222.*.* AS4808 Beijing, China BEIJING - CHINA MOBILE AS979 -> CMI Geographic Route: Japan -> Beijing ASN Path: AS979 -> AS58453 -> AS9808 -> AS56048 1 1.07ms 64.83.*.* AS979 Tokyo, Japan 2 4.25ms 10.81.*.* RFC1918 4 0.72ms 223.118.*.* AS58453 CMI 5-6 0.48ms 223.119.*.* AS58453 Tokyo, Japan CMI 7 50.67ms 223.120.*.* AS58453 Beijing, China CMI 8-9 50.51ms 221.183.*.* AS9808 Beijing, China 12-15 54.51ms 211.136.*.* AS56048 Beijing, China 17 53.66ms 211.136.*.* AS56048 Beijing, China SHANGHAI - CHINA TELECOM AS979 -> CTG GIA Geographic Route: Japan -> Shanghai ASN Path: AS979 -> AS23764 -> AS4809 -> AS4134 -> AS4812 1 0.88ms 64.83.*.* AS979 Tokyo, Japan 2 0.37ms 10.81.*.* RFC1918 4 0.52ms 69.194.*.* China Telecom 5-7 0.44ms 203.128.*.* AS23764 Tokyo, Japan China Telecom Global 8 27.81ms 203.22.*.* [CTG-CN] Tokyo, Japan 9 46.52ms 59.43.*.* AS4809 [CN2-BackBone] Shanghai, China 10 36.57ms 202.97.*.* AS4134 [CHINANET-BB] Shanghai, China 12 44.95ms 101.95.*.* AS4812 Shanghai, China 18 42.40ms 101.226.*.* AS4812 Shanghai, China SHANGHAI - CHINA UNICOM AS979 -> AS10099 Geographic Route: Japan -> Shanghai ASN Path: AS979 -> AS10099 -> AS4837 -> AS140979 1 2.17ms 64.83.*.* AS979 Tokyo, Japan 2 0.44ms 10.81.*.* RFC1918 5-6 1.09ms 203.160.*.* AS10099 Tokyo, Japan China Unicom Global 7 2.36ms 61.14.*.* Tokyo, Japan 9 43.81ms 219.158.*.* AS4837 Shanghai, China 10 48.93ms 219.158.*.* AS4837 Beijing, China 18 33.73ms 112.64.*.* AS140979 Shanghai, China SHANGHAI - CHINA MOBILE AS979 -> CMI Geographic Route: Japan -> Shanghai ASN Path: AS979 -> AS58453 -> AS9808 1 1.30ms 64.83.*.* AS979 Tokyo, Japan 2 1.07ms 10.81.*.* RFC1918 4 0.80ms 223.118.*.* AS58453 CMI 5-6 0.48ms 223.119.*.* AS58453 Tokyo, Japan CMI 7 31.17ms 223.120.*.* AS58453 Shanghai, China CMI 8-10 32.41ms 221.183.*.* AS9808 Shanghai, China 13 36.16ms 117.185.*.* AS9808 Shanghai, China GUANGDONG - CHINA TELECOM AS979 -> CTG GIA Geographic Route: Japan -> Guangdong ASN Path: AS979 -> AS23764 -> AS4809 -> AS4134 -> AS58466 1 0.83ms 64.83.*.* AS979 Tokyo, Japan 2 0.75ms 10.81.*.* RFC1918 4 2.30ms 69.194.*.* China Telecom 5-7 0.44ms 203.128.*.* AS23764 Tokyo, Japan China Telecom Global 8 28.05ms 203.22.*.* [CTG-CN] Tokyo, Japan 10 51.93ms 59.43.*.* AS4809 [CN2-BackBone] Guangzhou, China 11-12 53.41ms 202.97.*.* AS4134 Guangzhou, China 13 52.78ms 113.96.*.* AS4134 Guangzhou, China 15 64.40ms 14.215.*.* AS4134 Guangzhou, China 19 57.34ms 14.22.*.* AS58466 Guangzhou, China GUANGDONG - CHINA UNICOM AS979 -> AS10099 Geographic Route: Japan -> Shanghai -> Guangdong ASN Path: AS979 -> AS10099 -> AS4837 -> AS17816 -> AS136958 1 0.99ms 64.83.*.* AS979 Tokyo, Japan 2 6.34ms 10.81.*.* RFC1918 5-6 1.12ms 203.160.*.* AS10099 Tokyo, Japan China Unicom Global 7 2.02ms 61.14.*.* Tokyo, Japan 9-11 50.81ms 219.158.*.* AS4837 Shanghai, China 12 60.56ms 219.158.*.* AS4837 Guangzhou, China 13 61.76ms 221.4.*.* AS17816 Guangzhou, China 14 60.15ms 120.80.*.* AS17816 Guangzhou, China 16 58.60ms 122.13.*.* AS136958 Guangzhou, China GUANGDONG - CHINA MOBILE AS979 -> CMI Geographic Route: Japan -> Guangdong ASN Path: AS979 -> AS58453 -> AS9808 -> AS56040 1 0.94ms 64.83.*.* AS979 Tokyo, Japan 2 1.06ms 10.81.*.* RFC1918 4 0.59ms 223.118.*.* AS58453 CMI 5-6 0.67ms 223.119.*.* AS58453 Tokyo, Japan CMI 7 71.47ms 223.120.*.* AS58453 Guangzhou, China CMI 8-11 59.68ms 221.183.*.* AS9808 Guangzhou, China 12-13 70.06ms 211.136.*.* AS56040 Guangzhou, China 14-15 98.19ms 120.198.*.* AS56040 Guangzhou, China 18 80.72ms 211.139.*.* AS56040 Guangzhou, China
Full NodeQuality Report
View the full NodeQuality report
Quick Take
The hardware is nothing special, and the 100Mbps port + 400GB monthly traffic are definitely the biggest limitations.
But that’s not really why you’d buy this VPS.
The interesting part is the routing back to mainland China:
China Telecom → CTG GIA
China Unicom → AS10099
China Mobile → CMI
Latency also looks pretty decent for a Tokyo VPS. Shanghai is roughly in the 30–40ms range, while Guangdong is mostly around 60–80ms depending on the ISP. Guangxi Unicom even showed around 40ms in this test.
The IP is also surprisingly clean. Netflix, Disney+, TikTok, YouTube, Amazon Prime Video, Reddit and ChatGPT all showed native Japanese unlocks in this particular test.
So yeah, this isn’t a VPS you buy for CPU, storage, or bandwidth.
You’re basically paying for the routes.
For someone looking for a small personal Tokyo VPS with optimized connectivity back to China, JP.TKY.TRI.Basic is actually pretty interesting — assuming you can even get one in stock.
评论