I actually wanted to post this in the other thread about china and how they stole traffic from USA, but just can't find it... Not even per search engine. Anyway. I was inspecting my traffic and found that my traffic goes four times through the atlantic. That can't be correct behavior, can it? It goes from Luxembourg to USA to Netherlands and back to USA. For example, windows tracert tool: Code: tracert www.google.com Tracing route to www.google.com [216.58.208.36] over a maximum of 30 hops: 1 30 ms 29 ms 28 ms lu-003.staticnetcontent.com [94.242.249.114] 2 29 ms 30 ms 35 ms ip-static-94-242-249-113.server.lu [94.242.249.113] 3 28 ms 31 ms 29 ms root-ipt-gw.iptransit.com [204.26.60.28] 4 34 ms 33 ms 32 ms 100g-lux.de-r1.iptransit.com [199.59.206.177] 5 40 ms 41 ms 40 ms 100g-fra.xcore-ams1-ipt-r1.iptransit.com [199.59.206.146] 6 44 ms 40 ms 40 ms xcore-ams1-ipt-r2.iptransit.com [204.26.60.127] 7 39 ms 38 ms 39 ms core1.ams.net.google.com [80.249.208.247] 8 44 ms 39 ms 38 ms 108.170.241.140 9 41 ms 39 ms 39 ms 216.239.42.213 10 45 ms 45 ms 45 ms 209.85.244.159 11 46 ms 45 ms 46 ms 108.170.236.248 12 44 ms 45 ms 45 ms 108.170.251.129 13 44 ms 44 ms 44 ms 66.249.94.135 14 44 ms 45 ms 44 ms fra15s12-in-f4.1e100.net [216.58.208.36] (This is through VPN, so it is irrelevant if you see any IPs.) EDIT: Related question: The tracert took about 2 minutes, wth? It's peculiarly slower through the VPN, but pings at the end are almost ten times better and there are about half as much servers as without... Man!... I don't understand networking...
The availability of multiple routes could cause this. Try doing tracert with just one probe, instead of the default three simultaneous probes. In Linux traceroute, that's "-N 1".
There's no option for that. Only: Code: Options: -d Do not resolve addresses to hostnames. -h maximum_hops Maximum number of hops to search for target. -j host-list Loose source route along host-list (IPv4-only). -w timeout Wait timeout milliseconds for each reply. -R Trace round-trip path (IPv6-only). -S srcaddr Source address to use (IPv6-only). -4 Force using IPv4. -6 Force using IPv6.
It doesn't seem to include traceroute. EDIT: It's the same from my phone, btw. Using itraceroute app (android)
There's a web site that will perform traceroute for you: https://www.ipaddressguide.com/traceroute Entering www.google.com on a non-VPN connection from USA - Midwest yields: traceroute to 172.217.15.100 (172.217.15.100), 10 hops max, 60 byte packets 1 216.182.226.236 (216.182.226.236) 20.144 ms 216.182.225.94 (216.182.225.94) 18.491 ms 216.182.226.242 (216.182.226.242) 51.985 ms 2 100.66.12.20 (100.66.12.20) 20.106 ms 100.66.8.194 (100.66.8.194) 60.941 ms 100.66.13.76 (100.66.13.76) 18.435 ms 3 100.66.15.28 (100.66.15.28 ) 14.608 ms 100.66.11.222 (100.66.11.222) 17.001 ms 100.66.15.130 (100.66.15.130) 10.850 ms 4 100.66.6.129 (100.66.6.129) 12.174 ms 100.66.6.87 (100.66.6.87) 16.283 ms 100.66.6.11 (100.66.6.11) 18.195 ms 5 100.66.4.33 (100.66.4.33) 17.424 ms 100.66.5.189 (100.66.5.189) 12.161 ms 100.66.4.217 (100.66.4.217) 13.898 ms 6 100.65.10.193 (100.65.10.193) 2.913 ms 100.65.11.65 (100.65.11.65) 0.444 ms 100.65.11.97 (100.65.11.97) 0.376 ms 7 52.93.24.54 (52.93.24.54) 2.911 ms 52.93.24.78 (52.93.24.78 ) 38.833 ms 52.93.28.219 (52.93.28.219) 1.134 ms 8 * 52.93.24.57 (52.93.24.57) 1.290 ms * 9 54.239.111.32 (54.239.111.32) 3.753 ms * 54.239.109.46 (54.239.109.46) 13.958 ms 10 52.93.27.150 (52.93.27.150) 17.613 ms * * Suspect all the route "bouncing around" you're experiencing is due to your VPN provider.
Yes, from their servers. Entering my IP shows that it is also bouncing around, though it never actually reaches my VPN IP. The site stops after ten hops. So I used this one instead an tracerouted my IP: https://traceroute-online.com/ Here are traceroutes without VPN From me to USA and from USA to me Here are traceroutes with VPN (German server for identical test) Germany to google austria to google france to google switzerland to google netherlands to google switzerland to google UK to google poland to google luxembourg to google Wth? Why are some to illogically routed? *puts tin foil hat on* five/nine/fourteen eyes? It looks like I should only use those countries who are not bouncing their traffic back and forth. Like Switzerland. Can someone confirm that this is the case for everyone in these countries?
This is a plot of a traceroute I got a while back from the VPN provider (Windscribe) It traces from someones work computer to the VPN server in luxembourg, I guess. But there's more to it. MAybe it goes through the tunnel So this is seems to be a big issue, if it is one.
Ok, but the lowest latency is shooting the packets four times through the ocean? Hard to believe. Which page could I test with instead?
Turns out the site I used has an incredible amount of bugs and is practically useless, atm. https://stefansundin.github.io/traceroute-mapper/ Google.nl also turns out to be in the USA and shows the hops (Every google site is in the USA) Reddit also shows the hops and microsoft is a total f*up - and that is the pages fault. This is totally wrong. Do you know a different program or website I could use? I already tried so many, and all are garbage.This one worked so good as long as I didn't look too close. The app on my phone is also bad. Everything is bad. Why do people bother making these?
There's a bunch of traceroute tools here: https://www.ittsystems.com/traceroute-alternatives/ . Most are free. Have you tried the Nirsoft tool mentioned in the article?
Using the Nirsoft tool I noticed something interesting. When I routetraced the Eset forum, forum.eset.com, the traced stopped when it hit a cloudfront relay server in the U.S. I know that forum site is hosted on Eset web servers in Slovakia to the best of my knowledge. So my best guess is tracing is being blocked depending on what backbone relay servers the traffic is hitting. Or from point of arrival at the cloudfront server, IPv6 is being used exclusively and the Nirsoft tool only supports IPv4 addressing.
Unfortunately, all of them are either not what I need or bad. The only program that is showing you a map is Open Visual Traceroute, but it needs JAVA Runtime environment, and I'm not going to get it. The only other tool showing a map is from a website that tests from their server only. The tool in Nirsoft is ok. It doesn't show a map, but tells you the country. (CountryTraceRoute.exe) But I don't see it mentioned in the article ..? It's incredibly fast too. I wonder why. Anyway, this shows that the site I used all the time has a bug. I already reported that. But not everything was wrong: Luxembourg to google Reddit.com also goes from Luxembourg to USA, to Netherlands and back to USA. Twitter.com does the same. As does JQuery.com, Doubleclick.net, google-analytics.com, googleapis.com Facebook.com goes from lux to USA, to ireland, to USA and then again to ireland. Quantserve.net just goes over UK to USA. As does adroll.com, newrelic.com Wikipedia.org goes to USA and back to Netherlands ads.exdynsrv.com goes straight to USA, skipping everything else most interestingly: yandex.ru first goes to USA, then netherlands and finally russia. ... (I just took some random URLs I found in my ad blocker) Is this all intended? Is the Internet just a huge clusterf? I mean, I do understand that there are nodes at important points, like amsterdam, where the traffic has to go through in order to skip the atlantic or something. But why does it first has to go to USA anyway? So much goes to USA first... *puts tin foil hat on* NSA
Oh, didn't see that post. Yeah, sometimes it hits a dead end and shows just a timeout for as much hops as you have configured. Like here, where I traced "microsoft.com" Also note that it is very different to when you trace "www.microsoft.com" View attachment 262443 (... I copied the ATTACH thing from the other post. Doesn't work) Anyway, this is the best tool I found so far.
When I traced an Eset IP address hosted in Russia, it when straight to it from my U.S. ISP with a few intermediate relay server hops in the EU. See the below. And yes, the Internet backbone is just a huge cluster of relay servers routing stuff all over. If there is an issue with one routing, it just choses another. I believe why a lot of network traffic is routed through the U.S. is because that is where the largest number of relay servers and networks are located.
It's probably just a speed thing (the most/closests servers, lowest ping etc...) why you traffic got routed the way like that (or reliability or costs saving or whatever....everyone renting bandwith and services from this and that...) But on the otherhand...you never know (my lilliput country for example renting most of it's webspace from USA......even tought we have perfectly good net here...hmmmmm.....)
Ok, but then why are people complaining if their traffic goes through China? The news, I mean. Sounds to me like this is the exact same thing, just not with china.
"Google services temporarily disrupted after traffic rerouted through China, Russia Google services temporarily went down on Monday after the site’s traffic was routed through other networks, including some in China and Russia. Traffic intended for Google addresses was rerouted to Russian network operator TransTelekom, China's Telecom Corp. and Nigerian provider MainOne, 'This incident at a minimum caused a massive denial of service to G Suite and Google Search,' ThousandEyes Ameet Naik wrote in a post. 'However, this also put valuable Google traffic in the hands of ISPs in countries with a long history of Internet surveillance.' It's unclear why traffic was rerouted through China and Russia..." https://thehill.com/policy/technology/416516-google-traffic-briefly-route-through-russia-china
