Leaderboard

Positive sample first: After the gateway it stays in M247 space most of the time, then gets handed off to what appears to be Cloudflare's Netherlands IX until finally arriving at the destination. # traceroute -T icanhazip.com traceroute to icanhazip.com (104.18.115.97), 30 hops max, 60 byte packets 1 10.27.6.1 (10.27.6.1) 11.186 ms 11.769 ms 11.774 ms 2 vlan27.as11.fra4.de.m247.com (141.98.102.177) 12.033 ms 12.152 ms 12.392 ms 3 vlan2919.agg2.fra4.de.m247.com (212.103.51.150) 11.761 ms 11.998 ms 12.004 ms 4 37.120.220.117 (37.120.220.117) 12.389 ms 12.388 ms 12.386 ms 5 193.27.15.223 (193.27.15.223) 11.994 ms 37.120.128.129 (37.120.128.129) 21.342 ms 37.120.128.253 (37.120.128.253) 12.092 ms 6 cloudflare.equinix-fr4.nl-ix.net (193.239.118.138) 13.699 ms 13.936 ms 12.635 ms 7 104.18.115.97 (104.18.115.97) 23.921 ms 172.70.248.3 (172.70.248.3) 12.412 ms 172.70.244.3 (172.70.244.3) 12.928 ms Negative sample: There is a redirection happening to another private v4 directly after the gateway, then through Leaseweb space until the handoff to Cloudflare at hop 8. Interesting detail, that redirection… traceroute -T iplocation.net traceroute to iplocation.net (188.114.97.10), 30 hops max, 60 byte packets 1 10.27.6.1 (10.27.6.1) 10.888 ms 10.888 ms 11.110 ms 2 10.252.128.1 (10.252.128.1) 19.355 ms 19.609 ms 19.611 ms 3 85.17.225.252 (85.17.225.252) 20.100 ms 20.102 ms 20.272 ms 4 po-123.ce16.ams-01.nl.leaseweb.net (212.7.201.132) 20.349 ms po-123.ce15.ams-01.nl.leaseweb.net (212.7.201.128) 20.270 ms 20.346 ms 5 81.17.35.64 (81.17.35.64) 20.832 ms 20.833 ms 81.17.35.60 (81.17.35.60) 20.576 ms 6 po-117.agg01.ams-01.leaseweb.net (31.31.38.40) 20.569 ms po-117.agg02.ams-01.leaseweb.net (31.31.38.44) 19.026 ms po-118.agg02.ams-01.leaseweb.net (31.31.38.46) 19.262 ms 7 et-49-1.agg01.ams-01.leaseweb.net (31.31.34.200) 19.498 ms et-49-1.bb01.fra-13.leaseweb.net (31.31.34.53) 26.650 ms 26.536 ms 8 162.158.84.10 (162.158.84.10) 27.514 ms 30.762 ms et-53-1.bb01.fra-13.leaseweb.net (31.31.34.51) 26.500 ms 9 172.70.244.3 (172.70.244.3) 27.738 ms 172.70.248.3 (172.70.248.3) 27.962 ms 27.960 ms 10 172.70.240.3 (172.70.240.3) 27.704 ms 27.602 ms 188.114.97.10 (188.114.97.10) 27.861 ms Second negative sample: Find the difference in these pictures… traceroute -T whatsmyip.com traceroute to whatsmyip.com (188.114.96.3), 30 hops max, 60 byte packets 1 10.27.6.1 (10.27.6.1) 11.139 ms 11.165 ms 11.165 ms 2 10.252.128.1 (10.252.128.1) 19.192 ms 19.440 ms 19.445 ms 3 85.17.225.252 (85.17.225.252) 19.675 ms 19.866 ms 19.885 ms 4 po-123.ce15.ams-01.nl.leaseweb.net (212.7.201.128) 19.845 ms 19.854 ms 19.873 ms 5 81.17.35.60 (81.17.35.60) 20.143 ms 81.17.35.62 (81.17.35.62) 20.390 ms 81.17.35.58 (81.17.35.58) 20.370 ms 6 po-118.agg01.ams-01.leaseweb.net (31.31.38.42) 20.129 ms 19.202 ms 19.197 ms 7 et-49-1.bb01.fra-13.leaseweb.net (31.31.34.53) 26.684 ms 26.388 ms et-50-1.agg01.fra-10.leaseweb.net (31.31.34.29) 26.145 ms 8 162.158.84.10 (162.158.84.10) 28.820 ms 28.846 ms 29.111 ms 9 162.158.84.10 (162.158.84.10) 29.117 ms 172.70.248.3 (172.70.248.3) 28.810 ms 162.158.84.10 (162.158.84.10) 28.353 ms 10 172.70.248.3 (172.70.248.3) 27.594 ms 188.114.96.3 (188.114.96.3) 28.788 ms 28.586 ms … they're the same pictures! Well, not exactly, but you'll notice a striking similarity. 10.252.128.1. This redirection is all that causes the ghost IP change. And it must be AirVPN-internal because there is no other explanation for a private v4 gateway followed by another private v4 address in the next hop. It ends up in a subnet from LeaseWeb in hop 3, and I believe the NL rerouting server is a LeaseWeb server (that's where the IP address you see comes from). Does the server IP address change? No. Is there a cause for concern? I strongly disagree. Should Staff be informed? I think so. At least to check on whether there are rerouting rules for these IP APIs. Don't panic. None you can directly connect to, no. Though, strictly speaking, a request rerouted through a rerouting server makes that rerouting server a de-facto exit node. Provide a list of servers and optionally a list of users reporting that. Probably a misconfiguration instead. They don't. Staff don't read every thread. See above, and by not panicking. Provide a list of servers you observed showing this IP API result.

It's German, but I highly recommend reading a bit through this. Try to get help from a fellow German with translation or use a translator. Your situation is frequently encountered here and you may have a few aces up your sleeve to counter this. https://www.abmahnwahn-dreipage.de/abmahnung-was-nun-was-tun/ I understand your uncertainty right now, but let's try using precise words to describe exactly what the VPN gets you. No, the encryption is for your traffic. The VPN server pseudonymizes your IP address: If your address is 1.2.3.4 and that of the VPN server is 5.6.7.8, any IP you connect to will see that the connection comes from 5.6.7.8. No VPN guarantees your safety. But it helps, especially with the correct configuration. They are. All servers can be used for P2P. The "kill switch" is called Network Lock here and is not a kill switch in the classical sense. It's a set of firewall rules that only allow connections to the VPN servers. This is more robust because the kill switch is a reactive technique (reacts to a failed ping or a change of IP address, etc.) while the firewall is proactive (rules are rules and are application-independent). IPLeak is AirVPN's own IP API. But people use others as well. Start your journey with Mr. LZ1's New User Guide. There's good detail for people not familiar with VPNs. Welcome to AirVPN! Happy to have you here, enjoy your stay

Hello! We're very glad to inform you that a new 1 Gbit/s full duplex server located in Dublin, Ireland, is available: Minchir. The AirVPN client will show automatically the new server; if you use any other OpenVPN client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 UDP for WireGuard. Minchir supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. 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/minchir Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team