Site icon Beast Net

ExpressVPN Mac test in China-20200901

It’s already September today and time really does go by fast! Have you all brought more to your studies, work, investments, entertainment, and other behaviors this year by going over the wall? The hesitation epidemic at the beginning of the year may have been more shut down when by flipping the wall did you gain more perspective on the epidemic than you did on people. Then came the Hong Kong incident, the US-China trade, the US net-clearing operation, and so on. There are many things inside the wall you can not get the latest multi-directional perspective, but after the wall, you will have equal access to information as anyone in the world, but you have to slowly learn and develop to recognize the news, analyze the news, deep understanding of the background logic of the news. This blog will act as a bridge to the world of knowledge, maybe I’m overestimating the usefulness of this blog, but at least that’s what I think!

Note: There will be a major firewall upgrade blocking event in late September – early October!

Barry: I’ve been hoping to convey a message to my readers that the firewall will be around for the foreseeable future; with it, using any VPN or other tool in China is a dynamic process and there’s no one-and-done solution. That’s why I keep updating the [Daily Test] section. The purpose of the test is to tell you the real usage of the changed VPN at the moment, whether it’s available or not, and I’ll be honest about it. In order to speed up the testing, I will be running only SpeedTest tests on it as it is only a reference for the speed test.

ExpressVPN Last 6 test reports:[See More]Checking out multiple test reports can help you understand more effectively how this VPN works in the long run.

Local Device and Network:Macbook/200M/WiFi;
Speedtest Ping:7ms;Download:227Mbps;Upload:20Mbps;


ExpressVPN – Macbook Test in China:

Starting Time: Sep 1, 2020, 1:35 PM

The following is official recommend method;
Protocol: Auto

Hong Kong – 4: First success(Time efficiency: 1m8s)
Speedtest Ping: 190ms. Download: 12.8Mbps. Upload: 1.6Mbps.

Japan – Yokohama: First success(Time efficiency: 3m10s)
Speedtest Ping: 79ms. Download: 15.5Mbps. Upload: 4.58Mbps.

Singapore – Marina Bay: First success(Time efficiency: 16s)
Speedtest Ping: 134ms. Download: 115Mbps. Upload: 0.51Mbps.

USA – Los Angeles – 5: First success(Time efficiency: 45s)
Speedtest Ping: 154ms. Download: 13.6Mbps. Upload: 3.72Mbps.


The following is unofficial recommend method;
Servers: Random
Protocol: IKEv2

USA – Santa Monica: Failed. (Try once)
USA – New York: First success. (Time efficiency: 41s)
Speedtest Ping: 258ms. Download: 12.6Mbps. Upload: 3.4Mbps.
Note: There was a disconnection after this server connected, but it automatically connected again immediately after the disconnection.

USA – San Francisco: First success. (Time efficiency: 8s)
Speedtest Ping: 263ms. Download: 4.64Mbps. Upload: 2.09Mbps.

USA – Chicago: Failed. (Try once)
USA – Washington DC: Failed. (Try once) 
USA – Dallas: First success. (Time efficiency: 7s)
Speedtest Ping: 232ms. Download: 9.06Mbps. Upload: 3.54Mbps.

USA – Miami: Failed. (Try once)
USA – Los Angeles – 3: First success. (Time efficiency: 40s)
Speedtest Ping: 158ms. Download: 10.2Mbps. Upload: 3.93Mbps.

USA – New Jeresey – 1: Failed. (Try once)
USA – Denver: Failed. (Try once)
USA – Tampa – 1: First success. (Time efficiency: 1m20s)
Speedtest Ping: 158ms. Download: 10.2Mbps. Upload: 3.93Mbps.

USA – New York – 2: Failed. (Try once)
USA – Hollywood: Failed. (Try once)
USA – Atlanta: Failed. (Try once)
Canada – Toronto – 2: First success. (Time efficiency: 1m20s)
Speedtest Ping: 223ms. Download: 6.43Mbps. Upload: 4.59Mbps.
Note: There was a disconnection after this server connected, but it automatically connected again immediately after the disconnection.

Canada – Toronto: First success. (Time efficiency: 1m10s)
Speedtest Ping: 227ms. Download: 5.82Mbps. Upload: 2.13Mbps.
Note: There was a disconnection after this server connected, but it automatically connected again immediately after the disconnection.

Canada – Montreal: Failed. (Try once)
Mexico: Failed. (Try once)
Panama: Failed. (Try once)
Peru: Failed. (Try once)
Hong Kong – 2: Failed. (Try once)
Japan – Tokyo – 2: First success. (Time efficiency: 1m30s)
Speedtest Ping: 176ms. Download: 2.07Mbps. Upload: 2.79Mbps.

Japan – Tokyo: First success. (Time efficiency: 60s)
Speedtest Ping: 54ms. Download: 21.1Mbps. Upload: 9.54Mbps.

Singapore – Jurong: First success. (Time efficiency: 55s)
Speedtest Ping: 254ms. Download: 2.98Mbps. Upload: 0.23Mbps.

Singapore – CBD: Failed. (Try once)
Australia – Sydney: First success. (Time efficiency: 8s)
Speedtest Ping: 250ms. Download: 8.39Mbps. Upload: 3.03Mbps.

Australia – Melbourne: Failed. (Try once)
Australia – Perth: Failed. (Try once)
Australia – Brisbane: Failed. (Try once)
Australia – Sydney – 2: Failed. (Try once)
Taiwan – 3: Failed. (Try once)

Summary: Today, I tested the situation of ExpressVPN in Macbook. From the test results, the connection success rate on Macbook through the IKEv2 protocol is much lower than Windows 10. But the official recommended connection method: “Auto+4 servers”, this method can still be used very smoothly, and the speed of Singapore-Marina Bay is pretty good. Today, I did not find a server with particularly good speed in the IKEv2 protocol, and I cannot continue to test and search because of time. But I hope that such a test can provide some reference meaning for everyone to use.

ExpressVPN Macbook Version: 7.11.2 (2);    Protocol: Auto/IKEv2
Today’s Test Score: ★ ★ ★


Exit mobile version