Chicago Cluster Rolling Restart

We are issuing a rolling restart to all servers in the Chicago cluster while investigating a performance-related issue being reported by Chicago customers. During this time, customers may be dropped from the network when their server in the cluster is restarted. You will be able to immediately reconnect to the service in Chicago and continue using your VPN service.

We take reports of unusual speed drops seriously and work hard to keep things run as fast, safe, and secure as possible.

Thank you.


> read more

July Server Maintenance

We will be restarting all server clusters over the hour to issue routine security and network updates.

During this time, service may be interrupted for up to 60 seconds at a particular location that we are working on.

You will be able to immediately reconnect to a different location, or can reconnect to the same location after a full minute has elapsed.
> read more

VikingVPN Client and Server Updates - July 2017

We are pleased to announce that the VikingVPN client has been updated with some significant changes to under-the-hood features.

We have updated the client from the 2.3.x fork to the 2.4.x fork. This is both to increase security and enable new features. All servers have been similarly switched from 2.3.x to 2.4.x.

We have adjusted our config files to increase compatibility with Apple OSX and the OpenVPN smartphone apps.

We have updated the security features used by our configs to avoid deprecated features that will be removed from OpenVPN version 2.5 in the future.

These updates are significant, but they are the first in a two-step process to enable a critical new feature, obfuscation (sometimes called "stealth" VPN). This feature (which will be on for all users by default) will encrypt the entire handshake process, which will make OpenVPN connections significantly harder to detect using deep-packet-inspection techniques. This should allow VikingVPN to break through ISP throttles and bypass OpenVPN blocks while sustaining no performance loss relative to our older configs.

> read more

Security Updates -- July 2017

We will be restarting all server clusters over the next few hours to issue routine security and network updates.

During this time, service may be interrupted for up to 60 seconds at a particular location that we are working on.

You will be able to immediately reconnect to a different location, or can reconnect to the same location after a full minute has elapsed.


> read more

VikingVPN Warrant Canary -- June 2017

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

July 1st 2017

VikingVPN, and it's parent company Viking Connections LLC, from the inception of the company to present day, has not received any of the following:
> read more

VikingVPN Warrant Canary -- May 2017

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

May 22nd 2017

VikingVPN, and it's parent company Viking Connections LLC, from the inception of the company to present day, has not received any of the following:
> read more

VikingVPN Warrant Canary April 2017

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

March 3rd 2017

VikingVPN, and it's parent company Viking Connections LLC, from the inception of the company to present day, has not received any of the following:
> read more

VikingVPN Warrant Canary -- March 2017

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

March 3rd 2017

VikingVPN, and it's parent company Viking Connections LLC, from the inception of the company to present day, has not received any of the following:

Requests for information - Civil or Criminal - We have never received a request for information on a specific user, nor any request for bulk user data, nor any request for metadata.

Requests to modify or weaken our services - We have never received a request to change our encryption, our security practices, or our protocols. This includes wiretap orders or implementing methods to identify users on our network.

Requests for private keys - We have never received a request for private VPN server keys, access to our website CA, or any code signing certificates we control. This includes all of our self-signed certificates in the chain used by our VPN network.

Specific Clandestine Warrants - We have never received a request under FISA 702 or Section 215 of the Patriot Act, nor any other clandestine court order.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYukeOAAoJEDyT+fmXUj/KuJwP/i9mrh05gid7JO721ZV61San
zbVHrHmbcE8mV11dszvmn0uh5c5EArmEdZpqW5FOrjI1Cz0vPBGO5tMHvWwYyrHw
Q57N0cxcO1nJS7G2fy8j2MBkIGWUdCdbOvdYikW0LvEkOB++IBnLU/3UqY//VD2r
f0oA0nM35VHowbbiGpOWz9rk9DhrnjB/xlFACG8Ph9+h0POLTNyzpn+xD9nOHqnr
zphhmfM10pfTwsiUWAd9qFBb2lZ9rxMGvT8by0qV6huLUx77nV2pfjsA4oE6zEPw
lmCtXBHoRUdEFdWL3xsQwYhM3bRfKJMRsKBOsAUtudYCuhgyi+y0nJyCmL04zS3O
uNgKhfpd2Gldgu+CkzR34NW+imBwKa4GTHjxZ4aC7UiCDqGQDPf8sq9ill0ertN3
WqJBTf5XOkH69LFKZZri+s/EpW/tZcAisKVrNlsHJd/FxqeVZ/USBiZXbntAjOWe
SawuunayHfMb+Xx3KDM8y+ZYHmhL7Y2Y+vaOcRM1lw0QWwXo3cUqkyeJfNUUO0+I
/xjGHzMvXOIL2jb/Oq2w/kMmcxdXqbTtOKSRSelYMhCWeJhi+KGN1OiscxhvNXax
91Q9pCSHDjriaS4oGZlYrP3LSqF6FAyHVNvecVxsK8uAGHP70aJFHNLPaP2M1FnZ
y8lvTyQ4NU7RQNKPq40f
=FWGY
-----END PGP SIGNATURE-----
> read more

Understanding Googles SHA-1 Collision and OpenVPN HMAC-SHA1

I have had a couple of people email me with grave concern over the settings that our network uses for our VPN, referring to the Google (and Dutch) research project that created a SHA-1 collision on two documents.

There are a lot of things to unpack here, and we need to understand the underlying mechanics of what is going on before we can make statements about the safety or unsafety of SHA-1 in different contexts.

What Google managed to do is extremely impressive, and it wasn't something I thought we would be seeing for at least another five years. A live collision is a huge step forward in the march to kill SHA-1 and it will likely accelerate adoption of SHA-2 and increase scrutiny of KECCAK and the SHA-3 subset of it, as standards organizations like to have two algorithms ready to go at any given moment, in case one of them is found to be insecure overnight and a replacement is immediately needed for the world to continue operating online.

> read more

Security-Updates-January-12th-2017

All VikingVPN servers are undergoing routine security updates and a rolling restart will be issued to all clusters over the next few hours. Expected downtime is less than 30 seconds. If you are disconnected from the VPN network in the next few hours, you should be able to immediately reconnect to the network and use the service as normal.

If unexpected downtime occurs, this post will updated with the details of this downtime.

> read more