3 ms·

I ain't changing my dns server to a server in Germany 6 50.242.148.34 (50.242.148.34) 11.825 ms 23.165 ms 11.936 ms 7 vlan60.csw1.sanjose1.level3.net (4.

I ain't changing my dns server to a server in Germany 6 50.242.148.34 (50.242.148.34) 11.825 ms 23.165 ms 11.936 ms 7 vlan60.csw1.sanjose1.level3.net (4.69.152.62) 167.163 ms 173.912 ms vlan80.csw3.sanjose1.level3.net (4.69.152.190) 179.634 ms 8 ae-61-61.ebr1.sanjose1.level3.net (4.69.153.1) 166.071 ms 166.300 ms ae-81-81.ebr1.sanjose1.level3.net (4.69.153.9) 166.493 ms 9 ae-2-2.ebr2.newyork1.level3.net (4.69.135.186) 166.700 ms 167.425 ms 168.243 ms 10 ae-62-62.csw1.newyork1.level3.net (4.69.148.34) 168.031 ms 167.538 ms ae-82-82.csw3.newyork1.level3.net (4.69.148.42) 168.819 ms 11 ae-71-71.ebr1.newyork1.level3.net (4.69.134.69) 168.592 ms ae-81-81.ebr1.newyork1.level3.net (4.69.134.73) 166.472 ms ae-61-61.ebr1.newyork1.level3.net (4.69.134.65) 167.677 ms 12 ae-41-41.ebr2.london1.level3.net (4.69.137.65) 167.766 ms ae-43-43.ebr2.london1.level3.net (4.69.137.73) 167.754 ms ae-42-42.ebr2.london1.level3.net (4.69.137.69) 167.882 ms 13 vlan103.ebr1.london1.level3.net (4.69.143.93) 167.297 ms vlan101.ebr1.london1.level3.net (4.69.143.85) 167.796 ms vlan103.ebr1.london1.level3.net (4.69.143.93) 166.458 ms 14 ae-23-23.ebr2.frankfurt1.level3.net (4.69.148.194) 165.179 ms ae-24-24.ebr2.frankfurt1.level3.net (4.69.148.198) 168.929 ms ae-23-23.ebr2.frankfurt1.level3.net (4.69.148.194) 165.134 ms 15 ae-72-72.csw2.frankfurt1.level3.net (4.69.140.22) 166.229 ms 171.583 ms ae-62-62.csw1.frankfurt1.level3.net (4.69.140.18) 166.542 ms 16 ae-3-80.edge4.frankfurt1.level3.net (4.69.154.136) 168.808 ms 167.824 ms ae-2-70.edge4.frankfurt1.level3.net (4.69.154.72) 177.082 ms 17 accelerated.edge4.frankfurt1.level3.net (212.162.25.6) 167.854 ms 182.773

deathanatos 12y ago
Because of the latency? Doesn't that traceroute indicate that most of the delay was just getting to Level 3 in San Jose, through your ISP? (Isn't that 50.242.148.34 node right between level3 and your ISP? Sadly it lacks a name, so hard to say who owns it.) Or because of trust? You're in the US.

deathanatos 12y ago

Because of the latency? Doesn't that traceroute indicate that most of the delay was just getting to Level 3 in San Jose, through your ISP? (Isn't that 50.242.148.34 node right between level3 and your ISP? Sadly it lacks a name, so hard to say who owns it.) Or because of trust? You're in the US.