The VikingVPN Bucharest Cluster is Live!


Our server cluster in Bucharest, Romania is now live and ready for use! This is our second cluster of servers in Europe and it brings our high speed VPN services to eastern Europe, the Balkan states, as well as parts of Russia and the Middle East.

As part of our commitment to be the fastest and most secure VPN service out there, we select new locations based on network resources and laws regarding logging policies. Romania perfectly fits into this model as the nation has a fantastic network infrastructure and they have recently thrown out their data retention laws as unconstitutional on July 8th 2014. English source and the original source is in Romanian

The addition of this server cluster also adds more value to your VikingVPN subscription. Since we allow 1 connection per server cluster, this increases the maximum number of simultaneous devices to 6 per account.

As always, we urge our customers to connect to the closest VPN servers for the best possible performance.

> read more

Patching for Linux glibc Ghost Vulnerability Completed

VikingVPN has completed a threat analysis and subsequent patch (if needed) of all systems related to the new Ghost vulnerability.

Our full analysis shows that none of our systems were vulnerable to attack on day 0.

Our web server does not utilize glibc. We also do not use PHP anywhere in the site. Our VPN servers have glibc present, and glibc is called by OpenVPN, but it does not use the vulnerable functions (gethostbyname, gethostbyname2). This means that the code related to the vulnerability is never used or executed by our systems.

We have updated the VPN servers to non-vulnerable versions of glibc as a precautionary measure.

Our final judgement is that no systems were vulnerable to the threat, and no risk to company or user data is or was present.

A more expansive article on the Ghost vulnerability will be posted to our Security Blog tonight.

> read more

We Are Doing Routine Maintenance on the Phoenix Cluster Tonight

We are currently doing routine maintenance on the Phoenix cluster. Users may be temporarily dropped from the network during this maintenance as some servers inside of the cluster need to be restarted. If you are disconnected from VikingVPN during this maintenance window, you should be able to immediately disconnect and reconnect to Phoenix and continue using the VPN normally.

Maintenance Is expected to be complete by Midnight EST.

> read more

VikingVPN Is Expanding with a New Server Cluster in the EU

Viking is committed to keeping speeds a high as possible for it's customer base. We have implemented a server buildout plan based on a clustering model, so that we have an ever-increasing territory with a high performance network, rather than a global slow one.

Our expansion plans include adding locations to better cover eastern Europe and the Asia-Pacific region.

Our expansions are triggered by servers in a nearby region hitting a certain density of users, which prompts us to expand to a new area. This means some of our existing customers will move to the new location because it is closer to them geographically (which usually means better performance) and it reduces the load on the existing cluster.

Amsterdam is our only EU cluster at this time. We are approaching the number of users on that node that will trigger an expansion in that region. This means that we are currently looking at datacenters in Eastern Europe for our next home. 

> read more

Speed Optimizations for OpenVPN Coming Soon

We have been working on an issue where some customers with very fast internet would see limited speeds when connecting to our servers. This problem seems to span multiple platforms, and multiple high speed internet providers.

We have found the underlying cause of the performance drag, and plan to implement the fix in the near future after we test the changes on all devices to be sure that no problems are introduced into the network with the change.

It bears repeating that this fix is only for very high speed customers (50+ Mbps) and will not impact most of our user base.

If you are a VikingVPN subscriber who thinks they are impacted by the current bug, you can contact us at customer care if you would like to implement the fix. We would appreciate the additional feedback from people before we roll out the change globally. This change may improve the performance of our service for all of our high speed broadband customers, especially those who are combining very high speeds with Wifi.

> read more

Internal Security Audit Completed - Smooth Sailing for VikingVPN

Our Christmas break was interrupted by the purported hack of Cyberghost, a large VPN provider. We have gone through a rigorous internal audit of all of our servers and services and found no issues with our servers or our network.

VikingVPN has routine internal audits of our entire infrastructure and occasional external audits of our non-critical infrastructure in an effort to create the hardest environment possible for attackers. This internal audit was generated by the press around the CG breach, as an extraordinary precaution to protect user data.

As it turns out, Cyberghost did not suffer a security breach, and the account information leaked from CG was via outside attack vectors like botnets or trojans on individual PCs.

> read more

Seattle Cluster Maintenance

*This issue has been resolved. The Seattle Cluster is alive and healthy once again.*

Our Seattle servers are currently under maintenance due to a problem with our host there. Due a problem with infrastructure in the datacenter in Seattle, our servers are operating at 1/10th of their normal speed. We are currently working to mitigate the issue.

If we have to take any of the live servers down during this process, we will automatically redirect users to other clusters to prevent service outages.

This post will be updated when maintenance is completed.

The issue with the host is resolved, and service to Seattle has been fully restored.

> read more

NYC Servers Being Upgraded

*This upgrade has been completed and the NYC cluster is operating normally*

Our server cluster in NYC is being migrated to a new SSAE16 data center for better connectivity and greater uptime. The NYC cluster will be down throughout this migration, and the cluster will be down for maintenance for approximately 8 hours.

At this time, we are redirecting all NYC customer traffic through our Chicago cluster.

When the migration is complete and the servers have been tested for functionality, we will update this post notifying our users that the NYC cluster has returned to normal.

Edit:

We have halted the redirection of users from NYC to Chicago. The NYC cluster is live once again in its new home. To connect to the cluster, just disconnect your current connection and connect using your NYC.ovpn file.


> read more

Seattle Cluster Restart

The Seattle cluster is being restarted to investigate a performance anomaly reported by some users. A full reboot of the cluster is required in order to be able to fully investigate the problem.

Downtime of the Seattle cluster is expected to be less than 1 minute. Reconnecting to the service should resolve any connectivity issues you have.

> read more

VikingVPN is Patching OpenVPN for a Denial of Service Attack Vulnerability

We are in the process of patching our servers for the recently discovered DOS vulnerability. Upgrading our servers to a new version of OpenVPN will require us to issue a rolling restart to all server clusters. This may cause clients to stop responding to network requests in the process. Downtime is expected to be approximately two seconds. Disconnecting and reconnecting to the service should instantly fix any issues.

The vulnerability is performance related only, and there is no risk to client information leaking as a result of the discovered bug.

A new version of OpenVPN is available fixing the issue (OpenVPN 2.3.6). This issue is mostly server-side so an upgrade from 2.3.5 is not going to be required to connect to our network.

You can read more about the vulnerability here:

> read more