WireGuard Status

This page includes updates on our WireGuard protocol implementation.   

Latest update (24/09/20): added new server in Switzerland (CH1); testing of 2-hops implementation is in progress and 2hop location setups will be added if all goes well in our testing. 

Previous updates:

08/08/20: Added new server in Italy
22/06/20: 
Added new server in France 
10/05/20: 
Netherlands server has been replaced due to a hardware failure 2 days ago. Either edit the specific server profile and replace its public key with the new one (RdXMnhvh9e1s5oOUMghTFp+oOBUobjirgGTRG0uVIX4=) or re-generate the profile(s) in WG Manager
06/04/20:
 Default server port in the generated config files has been changed to 51821. We also added support for multiple ports, so you can use any in the range 51820-51900. This may come handy if the default WireGuard port (51820) is blocked, which could be the case for some users in China. There is no need to generate new config files, you can change the port in the server profiles you alredy use. 
22/03/20: 
Added new San Francisco server
03/03/20: 
Added new Belgium and Japan servers
23/02/20: 
Added new Singapore server
17/01/20:
 Added new Sydney 2 gateway

08/01/20: 
the limit for WG devices has been increased for 3 to 6 for a single VPN account
10/07/19: 
added new server in Los Angeles
06/06/19: 
added WG server in LA (CN2, recommended for users in China) 
31/05/19: 
added guide for Windows
01/05/19: 
US East Coast Atlanta 2 and Miami 2 locations added
29/04/19: 
US West Coast - Seattle 2 location added
20/04/19: 
Australia (Melbourne) location added. 
08/04/19:
 Vancouver server has been replaced because of a hardware failure. To use it again, a new key for it must be generated with the WG manager tool
07/04/19: 
new locations added: Poland 2, Norway, US East - Miami, US Central - St. Louis, US Central - Denver. 
23/03/19: 
added guides for OpenWRT 18.06Linux
15/03/19:
 
added guides for AndroidiOSmacOS
10/03/19:
implementation is live. Initial setup guide for key management tool available here
10/03/19:
some pre-release fixes have been rolled-out, WG likely to be available later today (by end of day, UTC time)
03/03/19:
creation of this status page  

Active Tasks

03/03/19 [is][high] server side WG deployment [in progress]. ETA by end of first week of March, 15 servers will be available initially, more to be added gradually
03/03/19 [o][high] implementation of preshared key as an option [in progress] 

Completed Tasks (recent)

07/04/19 [is][med] new locations added: Poland 2, Norway, US East - Miami, US Central - St. Louis, US Central - Denver. 
03/03/19 [o][med] tutorials for setting up a WG connection [done]. Available for OpenWRT, Linux, Android, iOS, macOS. 
03/03/19 [o][high] front-end implementation of key management tool [done]. Live implementation ready on 10/03/19
11/11/18 [is/o][high] Internal development (backend API, frontend key management tool, servers): internal development started in November as per our announcement, everything finalized at the end of February 2019. 

Privacy considerations: by design, WireGuard isn't suitable for none/limited logging policies. Specifically, last public IP of user would be saved on the server used to connect to and it can't be removed within a day as per our current privacy policy. At a later date we will likely make some tweaks to the source code to sanitize or remove the last used public IP. 

WireGuard® is a registered trademark of Jason A. Donenfeld.


Other tutorials: