Leaderboard

Hiya, I am running the new version fine now. Although, by "fine" I mean it's still buggy, but that is just eddie I think. I have totally migrated my data by hand from one mac to another, new user account, fresh start in case any glitches were in the old account. (I didn't do this for Eddie's sake, I had to move to a new machine anyway and took the chance to create a fresh user account). Eddie is working a bit better I think, but it still occasionally freezes/hangs if I click too quick to cancel or change a connection etc. All in all it's more than usable though, and AirVPN is such a cool organisation that I will live with the occasional glitches! They usually happen after the machine goes into sleep, so I am playing with other settings (tried that before but worth doing again with new Eddie version).

Hello! We're very glad to inform you that a server located in Stockholm (SE) has been upgraded: Ain. Server is now connected to a 10 Gbit/s line and port, while the motherboard has been replaced with a more powerful CPU. IP addresses remain the same. You don't need to re-generate configuration files, even if you don't run our software. As usual the server includes load balancing between daemons to squeeze as much bandwidth as possible from the 10 Gbit/s line. The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP. Just like every other Air server, Ain supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3 and tls-crypt. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. You can check the server status as usual in our real time servers monitor: https://airvpn.org/servers/Ain Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

What exactly is it you want to read, Mr. Trump? CAPTCHAs are to be expected on publically accessible VPNs and proxys. They're easy to abuse by anyone. ToS stating abuse is forbidden are not a protective shield against this. A bad actor, well, well. I can't see an individual or one group trying to influence something there. It's much more likely that a few AirVPN accounts used some VPN servers for something scripted, and some algorithm at Google deduced that, in order to limit the effects of this, it's best if some of these v4 IPs or subnets are shown CAPTCHAs. I have a theory that, with proper v6 connectivity, such things could be limited to specific offending v6 addresses, meaning, everyone not out to attack the internet can actually enjoy a CAPTCHA-free experience while the attackers are stuck with them. If you restrict one v4 address, you are restricting everyone NATting through this v4 address. From the inside this looks exactly like what you perceive: "Look, now they want to silence VPN users", when in reality one bad apple simply spoiled the barrel.

Dutch servers too. Big captas. Select stairs, right 😒