SVPN VSA-500X Appliance Test

SVPN Appliance

SVPN is a new startup offering a unique Secure Virtual Private Network service, the SVPN VSA-500X is currently in beta testing, and it makes your internet connection private and secure, preventing spying by ISPs, governments and cybercriminals.

It also stops malware, tracking and threats.

With the 500X you get full-time strong encryption and privacy, and websites will see your connection coming from a location of your choice, hiding your real location.

SVPN Benefits

About the Test

I tested two VSA-500X’s from my Canadian ISP, one in London, UK and one in Virginia, US.  Both were tested over UDP with AES-256-CBC data channels but you can also get service in TCP on port 443 and you can choose between AES-128, AES-192 and AES-256 ciphers.

You can choose from these locations, more coming after the beta:

U.S. East Coast
U.S. West Coast
Central Canada
London, UK
Frankfurt, Germany
Ireland, EU
Seoul, Korea
Singapore, SE Asia
Sydney, Australia
Tokyo, Japan
Mumbai, India

SVPN U.K and U.S. speed tests from Canadian origin

I tested the VSA-500X from my 100Mbps / 10Mbps cable connection at home to see how it performs for a typical consumer.

Baseline speed test without SVPN from Canadian ISP – dslreports.com/speedtest

SVPN Canadian Baseline

SVPN Virginia, United States speed test – dslreports.com/speedtest

SVPN U.S. East

SVPN London, United Kingdom speed test – dslreports.com/speedtest

SVPN London U.K.

SVPN U.K. and U.S. pings tests from Canadian origin

First, a baseline ping without SVPN from my Canadian ISP

Pinging google.ca [172.217.1.35] with 32 bytes of data:
Reply from 172.217.1.35: bytes=32 time=30ms TTL=52
Reply from 172.217.1.35: bytes=32 time=56ms TTL=53
Reply from 172.217.1.35: bytes=32 time=29ms TTL=52
Reply from 172.217.1.35: bytes=32 time=43ms TTL=52

Ping statistics for 172.217.1.35:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 56ms, Average = 39ms

Baseline ping x 100 without SVPN from my Canadian ISP

Ping statistics for 216.58.192.163:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 121ms, Average = 34ms

SVPN Virginia, United States Ping – google.com

Pinging google.com [172.217.7.238] with 32 bytes of data:
Reply from 172.217.7.238: bytes=32 time=51ms TTL=48
Reply from 172.217.7.238: bytes=32 time=60ms TTL=48
Reply from 172.217.7.238: bytes=32 time=59ms TTL=48
Reply from 172.217.7.238: bytes=32 time=48ms TTL=48

Ping statistics for 172.217.7.238:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 60ms, Average = 54ms

SVPN Virginia, United States – Ping x 100 – google.com

Ping statistics for 172.217.7.238:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 65ms, Average = 50ms

SVPN London, United Kingdom – Ping Test – google.co.uk

Pinging google.co.uk [216.58.198.67] with 32 bytes of data:
Reply from 216.58.198.67: bytes=32 time=112ms TTL=48
Reply from 216.58.198.67: bytes=32 time=109ms TTL=48
Reply from 216.58.198.67: bytes=32 time=108ms TTL=48
Reply from 216.58.198.67: bytes=32 time=118ms TTL=48

Ping statistics for 216.58.198.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 108ms, Maximum = 118ms, Average = 111ms

SVPN London, United Kingdom – Ping x 100 – google.co.uk

Ping statistics for 216.58.198.67:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 103ms, Maximum = 119ms, Average = 106ms

SVPN CPU Utilization – YouTube Video James Arthur @ 1080p

SVPN CPU

Streaming a 1080p on YouTube video barely touches the CPU.

SVPN CPU Utilization – 6 x speed tests averaging 92Mbps

SVPN CPU

CPU usage during six consecutive speed tests peaks at around 20% CPU utilization.

SVPN CPU Utilization – downloading a 1.4GiB torrent

SVPN CPU

The combination of CPU and speed tests show there’s tons of room for downloading at high speeds, as well as sustained streaming and downloads.  Even when I stacked all the streaming, downloading and torrent tests on top of each other everything ran smoothly.

Conclusion

I’ve been testing both the U.K. and U.S. service for about a week, and so far it has been very fast and I’ve not had any latency issues, in fact it’s very easy to forget you’re connected to an AES-256-bit tunnel at all and if this level of service is maintained then I’m sure it will become very popular.

Check out the launch offer at www.svpn.com

LEAVE A REPLY

Please enter your comment!
Please enter your name here