How about ion (krypt)? Share the PREMIUM VPS evaluation in San Jose to see how the actual performance is

Ion was founded in 2019. Its parent company, Krypt, was founded in 1998. It currently operates five data centers in the United States (Los Angeles, San Jose, Dallas, Hawaii) and Singapore. According to merchants' description, the return route of San Jose VPS is Unicom's 48374837. At present, the route is popular in the United States and Germany, and the United States is dominated by San Jose, Los Angeles' 4837 did not return home quickly.

The Big Bird Blog evaluates the VPS of the vendor's computer rooms in Los Angeles, Dallas and Hawaii before and after. Today, this article will evaluate the PREMIUM VPS in San Jose to see how the actual performance is. Interested partners can look around.

1. Official website

website: https://ion.krypt.asia

2. San Jose Premier

VPS features: KVM virtual, pure SSD array, 1Gbps bandwidth, 1 ipv4 by default

Cyclic discount code with 80% discount for quarterly payment and above: UGS81KV (Valid until July 25)

Test IP: 174.139.126.166

3. System parameters

CPU: Intel (R) Xeon (R) CPU E5-2690 v3 @ 2.60GHz, disk IO is about 119.7 MB/s

4. IP test

Tik Tok test:

Streaming media test:

IP quality test: the tested IP is still the native IP

5. Network test

Three network test:

iperf3 Network Speed Tests (IPv4):

Asia Speedtest.net:

Global Speedtest.net:

Server network speed measurement, Jiangsu Telecom 200M bandwidth, 19 test results.

IPv4 download test, Jiangsu Telecom 200M bandwidth, 19 test results.

Ping detection:

6. Routing

Telecom return: China Telecom forced China Unicom 4837 to return directly.

 2024-06-14 04:06:35 (110 MB/s) - ‘besttrace2021’ saved [9642256/9642256] ---------------------------------------------------------------------- Beijing Telecom traceroute to 219.141.147.210 (219.141.147.210), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.45 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  0.85 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.39.25  35.16 ms   AS4837  United States, California, San Jose, ChinaUnicom 4  219.158.6.89  208.23 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.113.134  201.25 ms   AS4837  China, Shanghai, ChinaUnicom 6  219.158.113.105  184.81 ms   AS4837  China, Shanghai, ChinaUnicom 7  * 8  219.158.99.14  166.87 ms   AS4837  China, Beijing, ChinaUnicom 9  219.158.34.202  149.55 ms   AS4837  China, Beijing, ChinaUnicom 10  * 11  * 12  2.254.120.106.static.bjtelecom.net (106.120.254.2)  217.75 ms   AS4847  China, Beijing, ChinaTelecom 13  bj141-147-210.bjtelecom.net (219.141.147.210)  244.47 ms   AS4847  China, Beijing, ChinaTelecom ---------------------------------------------------------------------- Shanghai Telecom traceroute to 202.96.209.133 (202.96.209.133), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.68 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  0.87 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.39.25  60.03 ms   AS4837  United States, California, San Jose, ChinaUnicom 4  219.158.116.237  200.94 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.8.185  185.89 ms   AS4837  China, Shanghai, ChinaUnicom 6  * 7  219.158.109.174  202.92 ms   AS4837  China, Shanghai, ChinaUnicom 8  * 9  * 10  61.152.25.9  232.66 ms   AS4812  China, Shanghai, ChinaTelecom 11  124.74.229.234  212.42 ms   AS4812  China, Shanghai, ChinaTelecom 12  ns-pd.online.sh.cn (202.96.209.133)  200.84 ms   AS4812  China, Shanghai, ChinaTelecom ---------------------------------------------------------------------- Shenzhen Telecom traceroute to 58.60.188.222 (58.60.188.222), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.28 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  0.83 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.39.25  60.51 ms   AS4837  United States, California, San Jose, ChinaUnicom 4  219.158.6.5  199.49 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.19.74  195.72 ms   AS4837  China, Shanghai, ChinaUnicom 6  219.158.19.81  183.56 ms   AS4837  China, Shanghai, ChinaUnicom 7  * 8  219.158.23.250  209.58 ms   AS4837  China, Guangdong, Guangzhou, ChinaUnicom 9  * 10  * 11  * 12  * 13  58.60.188.222  235.26 ms   AS4134  China, Guangdong, Shenzhen, ChinaTelecom

Telecommunication journey: Telecom backbone to Unicom 4837, directly connected to San Jose.

China Unicom's return journey: China Unicom's own backbone 4837.

 Beijing Unicom traceroute to 202.106.50.1 (202.106.50.1), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.53 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  1.10 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.43.97  60.28 ms   AS4837  China, Hong Kong, ChinaUnicom 4  219.158.116.233  248.59 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.6.205  246.46 ms   AS4837  China, Shanghai, ChinaUnicom 6  * 7  * 8  * 9  202.106.50.1  241.58 ms   AS4808  China, Beijing, ChinaUnicom ---------------------------------------------------------------------- Shanghai Unicom traceroute to 210.22.97.1 (210.22.97.1), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.59 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  1.12 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.43.97  62.94 ms   AS4837  China, Hong Kong, ChinaUnicom 4  219.158.97.177  191.48 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.113.122  224.42 ms   AS4837  China, Shanghai, ChinaUnicom 6  * 7  * 8  * 9  210.22.97.1  198.91 ms   AS17621  China, Shanghai, ChinaUnicom ---------------------------------------------------------------------- Shenzhen Unicom traceroute to 210.21.196.6 (210.21.196.6), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.29 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  0.80 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.39.25  53.62 ms   AS4837  United States, California, San Jose, ChinaUnicom 4  219.158.6.5  194.09 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.19.86  192.43 ms   AS4837  China, Shanghai, ChinaUnicom 6  * 7  * 8  157.18.0.238  235.03 ms   AS17816  China, Guangdong, Guangzhou, ChinaUnicom 9  120.80.144.34  239.47 ms   AS17623  China, Guangdong, Shenzhen, ChinaUnicom 10  dns2-ftcg.gdsz.cncnet.net (210.21.196.6)  257.68 ms   AS17623  China, Guangdong, Shenzhen, ChinaUnicom

China Unicom:

Mobile backhaul: China Unicom AS4837, which is also mandatory for mobile, connects directly to China. But I came back from Hong Kong.

 Beijing Mobile traceroute to 221.179.155.161 (221.179.155.161), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.49 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  0.95 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.43.97  36.60 ms   AS4837  China, Hong Kong, ChinaUnicom 4  219.158.6.89  198.08 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.113.134  203.38 ms   AS4837  China, Shanghai, ChinaUnicom 6  219.158.113.105  204.65 ms   AS4837  China, Shanghai, ChinaUnicom 7  219.158.6.169  224.15 ms   AS4837  China, Beijing, ChinaUnicom 8  219.158.10.202  220.36 ms   AS4837  China, Beijing, ChinaUnicom 9  * 10  221.183.94.37  223.08 ms   AS9808  China, Beijing, ChinaMobile 11  221.183.46.174  240.77 ms   AS9808  China, Beijing, ChinaMobile 12  221.183.130.134  252.46 ms   AS9808  China, Beijing, ChinaMobile 13  cachedns03.bj.chinamobile.com (221.179.155.161)  239.47 ms   AS56048  China, Beijing, ChinaMobile ---------------------------------------------------------------------- Shanghai Mobile traceroute to 211.136.112.200 (211.136.112.200), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.49 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  1.24 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.39.25  84.94 ms   AS4837  United States, California, San Jose, ChinaUnicom 4  219.158.97.177  222.77 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.113.118  233.95 ms   AS4837  China, Shanghai, ChinaUnicom 6  * 7  219.158.9.98  251.98 ms   AS4837  China, Shanghai, ChinaUnicom 8  221.183.123.109  236.33 ms   AS9808  China, Shanghai, ChinaMobile 9  221.183.90.253  229.32 ms   AS9808  China, Shanghai, ChinaMobile 10  * 11  * 12  211.136.112.252  214.51 ms   AS24400  China, Shanghai, ChinaMobile 13  211.136.112.200  209.59 ms   AS24400  China, Shanghai, ChinaMobile ---------------------------------------------------------------------- Shenzhen Mobile  traceroute to 120.196.165.24 (120.196.165.24), 30 hops max, 32 byte packets 1  customer.krypt.com (98.126.214.1)  0.35 ms   AS4213  United States, California, San Jose, vpls.com 2  ip-184-164-220-69.KRYPTCOLO.NET (184.164.220.69)  1.05 ms   AS35908  United States, California, Los Angeles, vpls.com 3  219.158.43.97  68.08 ms   AS4837  China, Hong Kong, ChinaUnicom 4  219.158.97.177  209.85 ms   AS4837  China, Shanghai, ChinaUnicom 5  219.158.6.209  205.91 ms   AS4837  China, Shanghai, ChinaUnicom 6  * 7  * 8  219.158.121.86  232.58 ms   AS4837  China, Guangdong, Guangzhou, ChinaUnicom 9  219.158.33.166  225.75 ms   AS4837  China, Guangdong, Guangzhou, ChinaUnicom 10  221.183.94.173  209.34 ms   AS9808  China, Guangdong, Guangzhou, ChinaMobile 11  221.183.71.78  200.15 ms   AS9808  China, Guangdong, Guangzhou, ChinaMobile 12  221.183.110.166  209.62 ms   AS9808  China, Guangdong, Guangzhou, ChinaMobile 13  ns6.gd.cnmobile.net (120.196.165.24)  232.87 ms   AS56040  China, Guangdong, Shenzhen, ChinaMobile

Mobile journey: the mobile cmi is directly connected to San Jose, and then connected to COgent, all the way to the computer room.

7. Performance test

Geekbench v5 CPU Benchmark:

Geekbench 6 Benchmark Test:

fio Disk Speed Tests:

IO Test:

8. Finally

VPS performance is pretty good, there is no problem in building a website.

The IP I got this time is a native IP, IP segment 98.126. **

Route: Three networks backhaul Unicom 4837, and the outgoing Telecom Unicom still goes to Unicom 4837, Mobile CMI.