Site icon Beast Net

PureVPN iPhone 3 Protocol Test in China

May 27, 2021 China VPN test, today I will test the international universal version of PureVPN’s APP in IOS/iPhone for mainland China. the IOS version of PureVPN is 8.14.2 and the protocol used for the connection is Automatic (when Auto protocol is turned off in the APP, you can manually select IPSec, IKEv2, TCP, UDP four kinds of protocols). The official advice to mainland China is to use manual configuration for IOS devices to connect, rather than APP direct connection, so let’s try to see if its APP can be successfully connected in the end. If the connection is not ideal under the Auto protocol, I will manually switch the protocol to IKEv2 and UDP to test the connection and will indicate the protocol options.

Follow the Twitter account to be the first to get the latest VPN test notification: 10Beasts_Barry

PureVPN Last 6 test articles guide: [View All]Check out the multiple test reports to help you understand the long-term usage of this VPN more effectively. This site has opened a new [Single test] column, a way to test “single device + single protocol + single server” through “fragmented” free time.


Starting Time: May 27, 2021, 2:29 PM
Local device and network:
iPhone / 300M China Telecom + 4G;
Version: 8.14.2;
Trotocol: Auto (IKEv2 and UDP);
Servers: Random;

Automatic Test in China:

Auto – USA – Chicago: Failed; (Try once, error: 408)
Auto – USA – New York: Failed; (Try once, error: 408)
Auto – USA – Los Angeles: Failed; (Try once, error: 408)
Auto – USA – Houston: Failed; (Try once, error: 408)
Auto – USA – Ashburn: Failed; (Try once, error: 408)
Auto – USA – Washington DC: Failed; (Try once, error: 408)
Auto – USA – Salt Lake City: Failed; (Try once, error: 408)
Auto – USA – San Francisco: Failed; (Try once, error: 408)
Auto – USA – Miami: Failed; (Try once, error: 408)
Auto – USA – Seattle: Failed; (Try once, error: 408)
Auto – USA – Phoenix: First success (Time efficiency: 8s);
Speedtest Ping: 170ms; Download: 313Mbps; Upload: 32.5Mbps;
SpeedTest Videos: 2160p;
Netflix Fast: 29Mbps;

Auto – USA – New Jersey: Failed; (Try once, error: 408)
Auto – USA – Atlanta: Failed; (Try once, error: 408)
Auto – UK – London: Failed; (Try once, error: 408)
Auto – UK – Manchester: Failed; (Try once, error: 408)
Auto – Netherlands – Amsterdam: Failed; (Try once, error: 408)
Auto – Germany – Frankfurt: Failed; (Try once, error: 408)
Auto – Canada – Vancouver: Failed; (Try once, error: 408)
Auto – Canada – Toronto: Failed; (Try once, error: 408)
Auto – Canada – Quebec: Failed; (Try once, error: 408)
Auto – Austrlia – Sydney: Failed; (Try once, error: 408)
Auto – Austrlia – Melbourne: Failed; (Try once, error: 408)
Auto – Austrlia – Perth: Failed; (Try once, error: 408)
Auto – Austrlia – Brisbane: Failed; (Try once, error: 408)


IKEv2 Test in China:

The above use of Automatic protocol option in the IOS server connection is not optimistic, the following I will switch the protocol to IKEv2 on the above server to test again to see if there is a difference between the two protocols server connection success rate.

IKEv2 – USA – Chicago: Failed; (Try once, error: 408)
IKEv2 – USA – New York: First success (Time efficiency: 5s);
Speedtest Ping: 240ms; Download: 200Mbps; Upload: 10.1Mbps;
SpeedTest Videos: 480p;
Netflix Fast: 42Mbps;

IKEv2 – USA – Los Angeles: Failed; (Try once, error: 408)
IKEv2 – USA – Houston: Failed; (Try once, error: 408)
IKEv2 – USA – Ashburn: Failed; (Try once, error: 408)
IKEv2 – USA – Washington DC: Failed; (Try once, error: 408)
IKEv2 – USA – Salt Lake City: Failed; (Try once, error: 408)
IKEv2 – USA – San Francisco: Failed; (Try once, error: 408)
IKEv2 – USA – Miami: Failed; (Try once, error: 408)
IKEv2 – USA – Seattle: Failed; (Try once, error: 408)
IKEv2 – USA – Phoenix: First success (Time efficiency: 5s);
Speedtest Ping: 171ms; Download: 321Mbps; Upload: 33.5Mbps;
SpeedTest Videos: 1080p;
Netflix Fast: 25Mbps;

IKEv2 – USA – New Jersey: Failed; (Try once, error: 408)
IKEv2 – USA – Atlanta: Failed; (Try once, error: 408)
IKEv2 – UK – London: First success (Time efficiency: 6s);
Speedtest Ping: Connected error;
Youtube Connection Speed: 6978Kbps;
Netflix Fast: 28Mbps;
Note: Since there was an error in the connection of this server in SpeedTest, I added YouTube connection speed as a reference in order to verify that the server is able to connect to YouTube;

IKEv2 – UK – Manchester: Failed; (Try once, error: 408)
IKEv2 – Netherlands – Amsterdam: Failed; (Try once, error: 408)
IKEv2 – Germany – Frankfurt: Failed; (Try once, error: 408)
IKEv2 – Canada – Vancouver: Failed; (Try once, error: 408)
IKEv2 – Canada – Toronto: First success (Time efficiency: 5s);
Speedtest Ping: 210ms; Download: 340Mbps; Upload: 36.5Mbps;
SpeedTest Videos: 480p;
Netflix Fast: 42Mbps;

IKEv2 – Canada – Quebec: Failed; (Try once, error: 408)
IKEv2 – Austrlia – Sydney: Failed; (Try once, error: 408)
IKEv2 – Austrlia – Melbourne: Failed; (Try once, error: 408)
IKEv2 – Austrlia – Perth: Failed; (Try once, error: 408)
IKEv2 – Austrlia – Brisbane: Failed; (Try once, error: 408)


UDP Test in China:

In the following I would like to test the above server again by UDP protocol. Since I know something about the post speed before and also to save time for testing, I will only publish the test results without testing its speed.

UDP – USA – Chicago: Failed; (Try once, error: 408)
UDP – USA – New York: First success (Time efficiency: 6s);
UDP – USA – Los Angeles: Failed; (Try once, error: 408)
UDP – USA – Houston: Failed; (Try once, error: 408)
UDP – USA – Ashburn: Failed; (Try once, error: 408)
UDP – USA – Washington DC: Failed; (Try once, error: 408)
UDP – USA – Salt Lake City: Failed; (Try once, error: 408)
UDP – USA – San Francisco: Failed; (Try once, error: 408)
UDP – USA – Miami: Failed; (Try once, error: 408)
UDP – USA – Seattle: Failed; (Try once, error: 408)
UDP – USA – Phoenix: First success (Time efficiency: 5s);
UDP – USA – New Jersey: Failed; (Try once, error: 408)
UDP – USA – Atlanta: Failed; (Try once, error: 408)
UDP – UK – London: First success (Time efficiency: 5s);
UDP – UK – Manchester: Failed; (Try once, error: 408)
UDP – Netherlands – Amsterdam: Failed; (Try once, error: 408)
UDP – Germany – Frankfurt: Failed; (Try once, error: 408)
UDP – Canada – Vancouver: Failed; (Try once, error: 408)
UDP – Canada – Toronto: Failed; (Try once, error: 408)
UDP – Canada – Quebec: First success (Time efficiency: 5s);
UDP – Austrlia – Sydney: Failed; (Try once, error: 408)
UDP – Austrlia – Melbourne: Failed; (Try once, error: 408)
UDP – Austrlia – Perth: Failed; (Try once, error: 408)
UDP – Austrlia – Brisbane: Failed; (Try once, error: 408)

Summary: The above is a test of the three protocol options for PureVPN on the iPhone. 24 servers were tested, and there are probably hundreds of servers listed in PureVPN’s IOS app, or at least certainly more than 100. If you look carefully, you will be able to find a server that you can connect to. The question now is whether the connection success of these servers is accidental or stable over time. I have added these servers to my collection and have been observing the connection of these servers for a long time. One thing that I need to praise the IOS side of PureVPN is that whenever the servers are successfully connected, their speed is very good.

Auto Server connection success rate: 1/24;
IKEv2 Server connection success rate: 4/24;
UDP Server connection success rate: 4/24;

IOS PureVPN Version: 8.14.2;
Protocol: Auto、IKEv2、UDP;
Server connection success rate score: ★ ★ ☆
Time efficiency score: ★ ★ ★ ★
Speed Test score: ★ ★ ★ ★ ☆


Exit mobile version