Windows support and privacy improvements for WireGuard

Releases By Nick Pestell | Posted on July 11, 2019

When picking a VPN service there are multiple criteria for evaluation, starting with questions like who owns the company behind it, whether your provider keeps logs and what happens with the data you share. Two further measures are usually on the top of the remaining list: the type of security the service provides and the connection speed you can achieve while using it.

On these two fronts, a newcomer protocol, WireGuard, offers the possibility for significant improvements to existing solutions for VPN services. While it is still in its test phase, and requires formal reviews and further audits before being ready for prime time, WireGuard clearly offers improved security and better speeds over currently-preferred protocols like OpenVPN.

Implementing WireGuard in our applications and offering its use through our service was a key priority for us last year. In a pioneering move we integrated it in our Android, iOS and macOS apps last December. Since then, feedback from our subscribers who have tested the solution have been overwhelmingly positive. As Windows was not officially supported by WireGuard at the time of our initial launch, adding the option to our app remained on our to-do list. After a recent release by the team behind the protocol, we are now happy to offer the test use of WireGuard in all of our applications.

WARNING: The WireGuard protocol is currently under heavy development and should be considered experimental. At this time we do not recommend using WireGuard except for testing or in situations where security is not critical. We keep our WireGuard VPN servers completely separate from our OpenVPN servers to ensure there are no security risks.

27/04/2020 update: Since its merge into Linux Kernel (v5.6) and the release of WireGuard 1.0, we consider the protocol to be ready for wide-scale use. We now offer WireGuard to all our subscribers.

More information:

Existing subscribers can start testing WireGuard simply by downloading the latest version of our Windows application and enabling WireGuard in the Settings (please see our guide and FAQ for more information). If you are not using IVPN yet, you can take advantage of our 3-day obligation-free trial option to test the service.

We have further news regarding our WireGuard implementation: As a VPN provider with a chief focus on privacy protection, we have considered and evaluated the possible risks of using the protocol during our tests. Security experts in our team have identified and solved multiple issues – including users' public IP being stored in memory indefinitely, the lack of real dynamic IP allocation and no ‘identity-hiding forward secrecy’ offered – and have taken significant steps towards eventually recommending WireGuard as a default VPN protocol to use. If you are curious about these technical solutions please review our article Using WireGuard for Privacy Protection.

If you have any feedback, questions or concerns about WireGuard for IVPN, our team is standing by for your message.

Looking forward to hearing your test impressions.

Nick Pestell &
the IVPN team

Apps Protocols Privacy WireGuard
We invite you to discuss this post in our Reddit community or on Twitter. You can also send your feedback to

Independent security audit concluded

By Nick Pestell


IVPN applications are now open source

By Viktor Vecsei


Beta IVPN Linux app released

By Viktor Vecsei

Introducing split tunnelling to IVPN for Windows Releases

Introducing split tunnelling to IVPN for Windows

Posted on September 14, 2021 by Viktor Vecsei

Split tunnels enable you to remain connected to your VPN while simultaneously accessing specific apps and services directly, bypassing the VPN tunnel. With this solution you can protect your privacy and connect to services that restrict or block customers who use commercial VPNs.
Extending two-factor authentication to IVPN apps Releases

Extending two-factor authentication to IVPN apps

Posted on September 7, 2021 by Viktor Vecsei

Last year we added a two-factor authentication (2FA) option for web-based account logins. This week we are extending the time-based OTP (one-time password) support to IVPN apps. If you have 2FA enabled on your account you will need to use the previously set up authentication method when logging in to apps.
Spotted a mistake or have an idea on how to improve this page?
Suggest an edit on GitHub.