Leaderboard
Popular Content
Showing content with the highest reputation on 09/08/21 in all areas
-
1 point
M247 misrepresenting true location of Barcelona Phoenix and Berlin Air Servers
User of AirVPN reacted to Daniel15 for a post in a topic
Thanks for posting about this. I never did get a response from the AirVPN staff about it. -
1 point
M247 misrepresenting true location of Barcelona Phoenix and Berlin Air Servers
Daniel15 reacted to User of AirVPN for a post in a topic
Some more pertinent information I found on another thread about this topic on the forums here, thought I would paste this to even further demonstrate that these servers are not located where M247 claims they are. all credits to user @Daniel15 as the below is originally his comment. Here's the link to his original comment on the other forum post if you want to read it there. It's been nearly two weeks since my original post, please Staff do take a look at this post and comment, thanks. Thats what i also stumbled apon. The RTT from Frankfurt <--> Berlin are _the same_, there is simply no way that the Berlin server is located in Berlin as the hop before is Frankfurt with the exact RTT. If i got, lets say 50ms towards Frankfurt, no way i got 50ms towards Berlin when its routed via Frankfurt before as last hop. I wont say Air is lying on their side, but pretty sure M247 is. @GrandeGiovanni I'm pretty sure you're right, and it's fairly trivial to verify. I have a server physically located in Los Angeles, in Psychz Networks' data center. If I ping Indus from that server, I get pings as low as ~0.40ms: $ ping indus.airservers.org PING indus.airservers.org (193.37.254.26) 56(84) bytes of data. 64 bytes from 193.37.254.26 (193.37.254.26): icmp_seq=1 ttl=59 time=0.421 ms 64 bytes from 193.37.254.26 (193.37.254.26): icmp_seq=2 ttl=59 time=0.554 ms 64 bytes from 193.37.254.26 (193.37.254.26): icmp_seq=3 ttl=59 time=0.450 ms 64 bytes from 193.37.254.26 (193.37.254.26): icmp_seq=4 ttl=59 time=0.403 ms ^C --- indus.airservers.org ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 0.403/0.457/0.554/0.058 ms I don't want to post any links because I'm afraid the forum system will mark this reply as spam, but you can verify this result by searching Google for "Psychz looking glass" and going to their Los Angeles looking glass. It'll let you send pings from their LA network. I can guarantee you that you will not get <0.5ms pings to a server that's physically in another location. I can't even get pings that low from one Los Angeles data center to othrer data centers in Los Angeles (ColoCrossing and QuadraNet)! Even the best networks are limited by the speed of light. Ping times are round-trip time, so a ping of 0.4ms means it takes 0.2ms to reach the server. Even if you assume a perfect network where data can flow at the speed of light with zero delays (which in reality is not possible), 0.2ms multiplied by the speed of light is only around 60 kilometers. That's less than 1/10 of the distance from Los Angeles to Phoenix! Fremont is around the same distance from Los Angeles as Phoenix. If I ping Aquila from the same server, the results are more what you'd expect for that distance: $ ping aquila.airservers.org PING aquila.airservers.org (199.249.223.129) 56(84) bytes of data. 64 bytes from 199.249.223.129 (199.249.223.129): icmp_seq=1 ttl=57 time=10.5 ms 64 bytes from 199.249.223.129 (199.249.223.129): icmp_seq=2 ttl=57 time=10.4 ms 64 bytes from 199.249.223.129 (199.249.223.129): icmp_seq=3 ttl=57 time=9.98 ms 64 bytes from 199.249.223.129 (199.249.223.129): icmp_seq=4 ttl=57 time=9.89 ms 64 bytes from 199.249.223.129 (199.249.223.129): icmp_seq=5 ttl=57 time=10.5 ms ^C --- aquila.airservers.org ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 9.885/10.258/10.544/0.270 ms From what I've seen so far, I can pretty much guarantee you that the servers are not in that data center. I've tried traceroutes from several providers using Cogent transit. If your VPN servers were actually on Cogent's network in Phoenix, I'd expect them to reach a Cogent router in Phoenix before seeing M247 in the traceroute, as Cogent will keep the traffic in their backbone network for as long as possible. However, in every single case I've seen, the traffic is only routed to Los Angeles on Cogent's network, before moving onto M247's network. Perhaps the most telling is doing a traceroute from somewhere east of Phoenix. Here's a traceroute I did from Chicago to Indus via Cogent's looking glass: traceroute to indus.airservers.org (193.37.254.26), 30 hops max, 60 byte packets 1 gi0-0-0-15.99.agr21.ord01.atlas.cogentco.com (66.250.250.89) 0.733 ms 0.731 ms 2 be2522.ccr42.ord01.atlas.cogentco.com (154.54.81.61) 1.145 ms 1.150 ms 3 be2831.ccr21.mci01.atlas.cogentco.com (154.54.42.165) 12.541 ms be2832.ccr22.mci01.atlas.cogentco.com (154.54.44.169) 16.431 ms 4 be3036.ccr22.den01.atlas.cogentco.com (154.54.31.89) 23.957 ms be3035.ccr21.den01.atlas.cogentco.com (154.54.5.89) 23.820 ms 5 be3046.ccr21.elp01.atlas.cogentco.com (154.54.0.45) 36.725 ms be3047.ccr21.elp01.atlas.cogentco.com (154.54.1.125) 36.957 ms 6 be2930.ccr32.phx01.atlas.cogentco.com (154.54.42.77) 44.976 ms be2929.ccr31.phx01.atlas.cogentco.com (154.54.42.65) 44.659 ms 7 be2932.ccr42.lax01.atlas.cogentco.com (154.54.45.162) 56.892 ms 56.898 ms 8 be3359.ccr41.lax05.atlas.cogentco.com (154.54.3.70) 56.621 ms be3243.ccr41.lax05.atlas.cogentco.com (154.54.27.118) 56.532 ms 9 38.104.85.170 (38.104.85.170) 56.920 ms 56.904 ms 10 * * 11 vlan2909.as09.lax1.us.m247.com (193.9.115.169) 56.739 ms vlan2921.as09.lax1.us.m247.com (193.9.115.167) 56.890 ms 12 * * 13 * * 14 * * Notice how hop 7 is going from Phoenix to Los Angeles? If the server was physically in Phoenix, there would be no reason to do that. All signs point to this server being physically located in Los Angeles. There's a possibility that they terminate the network in Los Angeles and then have private backhaul (like a GRE tunnel) from LA to Phoenix, but I wouldn't bet on it, especially with the 0.4ms pings from Los Angeles. I think you're correct about this too. I just got a VPS with a hosting provider with servers in Madrid (in the Interxion data center, using M247 as their transit provider) and pings to AirVPN "eridanus" are ~0.4ms. Similar to my Phoenix vs Los Angeles comment above, it's impossible to travel from Madrid to Barcelona in 0.4ms even at the speed of light. The actual ping time between a server in Barcelona and a server in Madrid should be around 7-9ms, which is what I see when I ping a server that's actually in Barcelona. You can see a comparison here: https://dnstools.ws/es/ping/lg.bcn.psychz.net,eridanus.airservers.org/ (these are ping times from a server in Madrid) Furthermore, ping times from Italy to AirVPN "Eridanus" are higher than ping times to Psychz's looking glass in Barcelona, which is also a sign that the server is in Madrid (since Madrid is further from Italy than Barcelona).