Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Contradicting traceroute results
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Contradicting traceroute results

I got a VPS from apexy.com (located in Zlin, CZ - so it should be FDCservers) and I am getting very weird results from my Czech home connection. Who should I blame in this case, my ISP, FDCservers or apexy.com?

traceroute to *** (198.105.122.*), 64 hops max, 52 byte packets
1 192.168.188.1 (192.168.188.1) 1.900 ms 1.515 ms 1.614 ms
2 * * *
3 ip-86-49-0-193.net.upcbroadband.cz (86.49.0.193) 9.636 ms 10.914 ms 11.189 ms
4 cz-prg01a-ra4-vla2010.net.upc.cz (84.116.222.201) 111.257 ms 109.507 ms 111.287 ms
5 84.116.135.1 (84.116.135.1) 111.184 ms 110.477 ms 135.926 ms
6 uk-lon01b-rd1-xe-1-2-2.aorta.net (84.116.132.17) 106.376 ms 107.799 ms 107.985 ms
7 us-nyc01c-rd1-pos-3-0-0.aorta.net (213.46.160.126) 125.680 ms
84.116.133.182 (84.116.133.182) 109.171 ms
84.116.137.34 (84.116.137.34) 110.044 ms
8 84.116.135.98 (84.116.135.98) 118.074 ms 105.760 ms 108.764 ms
9 nyk-b3-link.telia.net (62.115.13.73) 113.596 ms 112.564 ms 125.271 ms
10 nyk-bb2-link.telia.net (80.239.147.139) 111.329 ms
nyk-bb1-link.telia.net (80.91.248.173) 109.960 ms 108.239 ms
11 nyk-b5-link.telia.net (213.155.135.19) 112.687 ms
nyk-b5-link.telia.net (213.155.130.245) 108.538 ms 107.982 ms
12 cogent-ic-151338-nyk-b5.c.telia.net (213.248.85.106) 110.383 ms 110.097 ms 125.021 ms
13 be2061.ccr42.jfk02.atlas.cogentco.com (154.54.3.69) 110.585 ms 109.681 ms
be2060.ccr41.jfk02.atlas.cogentco.com (154.54.31.9) 109.292 ms
14 be2490.ccr42.lon13.atlas.cogentco.com (154.54.42.86) 184.456 ms
be2317.ccr41.lon13.atlas.cogentco.com (154.54.30.186) 193.236 ms 182.307 ms
15 be2488.ccr42.ams03.atlas.cogentco.com (154.54.39.109) 197.069 ms
be2194.ccr41.ams03.atlas.cogentco.com (130.117.50.242) 187.237 ms
be2488.ccr42.ams03.atlas.cogentco.com (154.54.39.109) 194.358 ms
16 be2186.ccr41.ham01.atlas.cogentco.com (154.54.74.122) 198.780 ms
be2187.ccr42.ham01.atlas.cogentco.com (154.54.74.126) 195.663 ms
be2186.ccr41.ham01.atlas.cogentco.com (154.54.74.122) 200.250 ms
17 be2078.ccr21.prg01.atlas.cogentco.com (130.117.0.166) 207.618 ms 206.014 ms
be2018.ccr21.prg01.atlas.cogentco.com (130.117.0.158) 212.103 ms
18 * * *
19 50.7.227.10 (50.7.227.10) 108.701 ms 110.649 ms 107.183 ms
20 198.105.122.100 (198.105.122.***) 112.120 ms 107.927 ms 109.304 ms

I especially do not know what to think about the JFK part of the traceroute, it can't going through JFK with a ping of 105-115ms. Traceroute to FDC Zlin seems fine with a ping of 14ms.

Comments

  • Blame UPC, they don't like peering.

  • FDCServers doesn't have a good network to start with, but both FDCServers (http://bgp.he.net/AS30058#_peers) and Liberty Global (http://bgp.he.net/AS6830#_peers) peer with "Dial Telecom, a.s." which should allow you to get a good connection and not do that weired route.

  • @MuZo Yeah, it does indeed go via Volny/Dialtelecom when I traceroute from FDC and my VPS to my router, but the latency varies.

    Yeah, UPC sometimes has very funky routing.
    The thing is that I don't know at all why there is such a difference between ping to my VPS and to FDC Zlin LG.

    VPS

    traceroute to xxx.net.upcbroadband.cz (89.103.131.xxx), 30 hops max, 60 byte packets
    1 198.105.122.2 (198.105.122.2) 0.037 ms 0.011 ms 0.009 ms
    2 bbr2--skysoft.dialtelecom.cz (82.100.0.105) 15.313 ms 15.516 ms 15.505 ms
    3 pni-prg-aorta.dialtelecom.cz (82.119.252.106) 107.862 ms 107.858 ms 107.844 ms
    4 cz-pra-pop123-ra2-vla2008.net.upc.cz (84.116.222.194) 106.188 ms 106.179 ms 106.391 ms
    5 ip-81-27-203-105.net.upcbroadband.cz (81.27.203.105) 97.499 ms 97.724 ms 97.712 ms
    6 xxx.net.upcbroadband.cz (89.103.131.xxx) 106.596 ms !X 105.265 ms !X 105.921 ms !X

    FDC Zlin LG

    traceroute to xxx.net.upcbroadband.cz (89.103.131.xxx), 30 hops max, 60 byte packets
    1 50.7.254.1 (50.7.254.1) 0.314 ms 0.314 ms 0.364 ms
    2 bbr2--skysoft.dialtelecom.cz (82.100.0.105) 4.964 ms 4.994 ms 5.027 ms
    3 pni-prg-aorta.dialtelecom.cz (82.119.252.106) 4.639 ms 4.641 ms 4.624 ms
    4 cz-pra-pop123-ra2-vla2008.net.upc.cz (84.116.222.194) 5.060 ms 5.044 ms 5.040 ms
    5 ip-81-27-203-105.net.upcbroadband.cz (81.27.203.105) 5.107 ms 5.110 ms 5.097 ms
    6 xxx.net.upcbroadband.cz (89.103.131.xxx) 12.873 ms !X 12.870 ms !X 12.856 ms !X

    Otherwise I did not really get why the traceroute from my computer has shown such a ridiculous route, which was bullshit anyways (via CZ->CZ via JFK despite 100ms ping). Is there any possibility of traceroute malfunction?

  • The source network specifies the route. Ask UPC why they are not using dialtelecom.
    Which route is being used if you traceroute "lg.zlin.fdcservers.net" from home?

    Regarding latency fluctuations you should ask Apexy.

Sign In or Register to comment.