Megalayer: 20% off on Hong Kong Alibaba hybrid servers - E3-1230/8GB/240G SSD/10M omnidirectional + 10M Alibaba Cloud bandwidth starting from RMB 638/month

This month, Megalayer provides Hong Kong Alibaba Hybrid Cloud Servers, with different hardware configuration models available. The machines are connected to Megalayer omnidirectional bandwidth and Hong Kong Alibaba Cloud lines at the same time, with 1 omnidirectional bandwidth IP + 1 Alibaba Cloud IP, 10M omnidirectional bandwidth + 10M Alibaba Cloud bandwidth, which can serve as the main backup for each other to ensure stable and uninterrupted business. From September 1st to 30th, merchants provide 20% discount codes for Hong Kong Alibaba Cloud Hybrid Servers. After the discount, the lowest E3+8GB memory model starts at 638 yuan per month.

The following is the configuration information of several Hong Kong Alibaba hybrid cloud servers.

The above discount codes are permanent discounts, and the renewal price is the same. The machine is generally activated quickly after payment. The member center integrates basic management functions. I purchased a machine with the minimum configuration. Here is the basic test information for your reference.

Host Configuration

The current test host configuration is E3-1230v3 CPU, 8GB memory, 240GB SSD hard disk, 2 lines and 2 IPs, and the installed operating system is the pure version of CentOS7.6.

Basic Tests

The picture below is the product management page of the merchant's integrated membership center, which includes server information, software information, basic management functions (power on/off, restart, VNC, reinstall system, etc.), and the parts not captured after the screenshot include traffic statistics, traffic usage chart, etc.

IO/Bandwidth Test

First use the most commonly used bench.sh one-click package. The SSD single-disk IO is good, and the bandwidth of 10M is consistent with the configuration.

Next, test it with Speedtest.

Partial streaming media unlock test information.

Outbound routing test

The merchant's Hong Kong data center has direct connections to the three domestic networks. The first is China Telecom. This screenshot is the omnidirectional bandwidth IP tested. The Alibaba Cloud IP goes through CN2+CTGNet for the outbound trip.

The following is China Unicom outbound. The screenshot is also an omnidirectional IP. Alibaba Cloud IP outbound uses CUII and AS9929

Finally, here is the outbound routing information of China Mobile. China Mobile’s outbound omnidirectional bandwidth IP is similar to Alibaba Cloud’s IP.

For the outbound trip of three networks, it would be better if the machine has two IPs, among which Alibaba Cloud IP and China Telecom and China Unicom IP are better.

Backhaul routing test

First use the one-click package to see the results. The summary is China Telecom 163/China Unicom 169/China Mobile CMI

The detailed information of the three-network return trip is posted below.

 Beijing Telecom traceroute to 219.141.147.210 (219.141.147.210), 30 hops max, 32 byte packets
 1 154.23.127.126 16.52 ms http: 403 http: 403
 2 10.252.0.22 0.62 ms http: 403 http: 403
 3 10.254.0.17 1.21 ms http: 403 http: 403
 4 10.248.10.14 1.76 ms http: 403 http: 403
 5 202.130.98.169 2.53 ms http: 403 http: 403
 6 115.160.187.85 2.87 ms http: 403 http: 403
 7 202.97.122.81 5.20 ms http: 403 http: 403
13 2.254.120.106.static.bjtelecom.net (106.120.254.2) 46.50 ms http: 403 http: 403
14 bj141-147-210.bjtelecom.net (219.141.147.210) 48.02 ms http: 403 http: 403
-------------------------------------------------------------------------------
Shanghai Telecom traceroute to 202.96.209.133 (202.96.209.133), 30 hops max, 32 byte packets
 1 154.23.127.126 15.59 ms http: 403 http: 403
 2 10.252.0.22 0.59 ms http: 403 http: 403
 3 10.254.0.17 1.12 ms http: 403 http: 403
 4 10.248.10.14 1.99 ms http: 403 http: 403
 5 202.130.98.169 2.71 ms http: 403 http: 403
 6 115.160.187.41 3.46 ms http: 403 http: 403
 7 203.215.232.129 6.27 ms http: 403 http: 403
12 180.169.255.122 35.13 ms http: 403 http: 403
13 ns-pd.online.sh.cn (202.96.209.133) 47.37 ms http: 403 http: 403
-------------------------------------------------------------------------------
Beijing Unicom traceroute to 202.106.50.1 (202.106.50.1), 30 hops max, 32 byte packets
 1 154.23.127.126 6.89 ms http: 403 http: 403
 2 10.252.0.22 0.58 ms http: 403 http: 403
 3 10.254.0.17 1.05 ms http: 403 http: 403
 4 10.248.10.14 1.81 ms http: 403 http: 403
 5 202.130.98.169 2.57 ms http: 403 http: 403
 6 115.160.187.85 3.07 ms http: 403 http: 403
 7 hnk-asp2-link.ip.twelve99.net (62.115.45.234) 3.10 ms http: 403 http: 403
 8 219.158.33.181 6.07 ms http: 403 http: 403
 9 219.158.10.49 11.58 ms http: 403 http: 403
10 219.158.3.185 10.65 ms http: 403 http: 403
11 219.158.3.93 9.42 ms http: 403 http: 403
14 202.106.50.1 39.24 ms http: 403 http: 403
-------------------------------------------------------------------------------
Shenzhen Unicom traceroute to 210.21.196.6 (210.21.196.6), 30 hops max, 32 byte packets
 1 154.23.127.126 12.12 ms http: 403 http: 403
 2 10.252.0.22 0.61 ms http: 403 http: 403
 3 10.254.0.17 1.11 ms http: 403 http: 403
 4 10.248.10.14 1.76 ms http: 403 http: 403
 5 202.130.98.169 2.70 ms http: 403 http: 403
 6 115.160.187.108 2.37 ms http: 403 http: 403
 7 219.158.39.117 5.22 ms http: 403 http: 403
 8 219.158.97.225 5.34 ms http: 403 http: 403
 9 219.158.20.97 14.97 ms http: 403 http: 403
10 219.158.3.213 14.43 ms http: 403 http: 403
12 120.82.0.162 12.53 ms http: 403 http: 403
13 120.80.144.38 14.74 ms http: 403 http: 403
14 dns2-ftcg.gdsz.cncnet.net (210.21.196.6) 13.20 ms http: 403 http: 403
-------------------------------------------------------------------------------
Shanghai Mobile traceroute to 211.136.112.200 (211.136.112.200), 30 hops max, 32 byte packets
 1 154.23.127.126 6.86 ms http: 403 http: 403
 2 10.252.0.22 0.50 ms http: 403 http: 403
 3 10.248.10.22 0.61 ms http: 403 http: 403
 4 62.25.252.241 2.78 ms http: 403 http: 403
 5 ae4-xcr1.hkg.cw.net (195.2.10.97) 4.27 ms http: 403 http: 403
 6 ae51-xcr1.sng.cw.net (195.2.10.178) 46.02 ms http: 403 http: 403
 7 223.121.2.61 36.51 ms http: 403 http: 403
 8 223.120.2.17 35.99 ms http: 403 http: 403
 9 223.120.3.186 60.62 ms http: 403 http: 403
10 221.183.89.170 62.13 ms http: 403 http: 403
11 221.183.89.33 62.33 ms http: 403 http: 403
12 *
13 221.183.39.138 64.58 ms http: 403 http: 403
14 211.136.190.234 65.02 ms http: 403 http: 403
15 211.136.112.252 64.87 ms http: 403 http: 403
16 211.136.112.200 65.39 ms http: 403 http: 403
-------------------------------------------------------------------------------
Shenzhen Mobile traceroute to 120.196.165.24 (120.196.165.24), 30 hops max, 32 byte packets
 1 154.23.127.126 42.77 ms http: 403 http: 403
 2 10.252.0.22 0.59 ms http: 403 http: 403
 3 10.248.10.22 0.40 ms http: 403 http: 403
 4 203.208.145.17 2.21 ms http: 403 http: 403
 5 203.208.151.93 2.41 ms http: 403 http: 403
 6 203.208.152.190 3.69 ms http: 403 http: 403
 7 223.120.2.117 4.51 ms http: 403 http: 403
 8 223.120.2.78 8.85 ms http: 403 http: 403
 9 221.183.55.82 10.37 ms http: 403 http: 403
10 221.183.92.17 34.37 ms http: 403 http: 403
11 *
12 221.183.71.78 35.95 ms http: 403 http: 403
13 221.183.110.166 37.48 ms http: 403 http: 403
14 ns6.gd.cnmobile.net (120.196.165.24) 34.72 ms http: 403 http: 403

Latency Test

The latency of the Hong Kong direct line is nothing to say. The average test value of 318 nodes from mainland China, Hong Kong, Macau and Taiwan is 47.1ms.

The Hong Kong server with two lines is just like the dual-line server sold in China. When the quality of one line is not good, you can use the other line to deploy the business. Some application scenarios may have such requirements. If the requirements are not high, you can also look at the conventional line models. You can choose optimized (including CN2)/omnidirectional/international bandwidth. The US server starts at 199 yuan/month, and the Hong Kong server starts at 399 yuan/month. For details, please refer to: https://www..net/30754.html