Trace route

Been wondering why my ping has increased in the last couple of days, so I ran a trace. Had 21 hops from my location in Texas to the server location in Canada. Is this normal, or is there something I am missing?

Comments

  • lvillage56 wrote: »
    Been wondering why my ping has increased in the last couple of days, so I ran a trace. Had 21 hops from my location in Texas to the server location in Canada. Is this normal, or is there something I am missing?

    what's the times for it?
  • lvillage56 wrote: »
    Been wondering why my ping has increased in the last couple of days, so I ran a trace. Had 21 hops from my location in Texas to the server location in Canada. Is this normal, or is there something I am missing?

    If you could, please copy and paste all the information you have when doing the trace route.
  • HerolSihao wrote: »
    If you could, please copy and paste all the information you have when doing the trace route.

    I'll do it.
    Tracing route to 161.6.200-74.q9.net [74.200.6.161]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms home [192.***.*.***]
    2 16 ms 13 ms 13 ms --
    3 13 ms 13 ms 13 ms --
    4 13 ms 13 ms 13 ms --
    5 43 ms 43 ms 43 ms 151.164.99.189
    6 45 ms 45 ms 45 ms asn577-bell-ca.eqchil.sbcglobal.net [151.164.250
    .242]
    7 56 ms 54 ms 55 ms CORE1-CHICAGO23_POS1-1.net.bell.ca [64.230.186.2
    33]
    8 56 ms 54 ms 56 ms core3-toronto47_POS0-2-0-0.net.bell.ca [64.230.1
    86.125]
    9 55 ms 57 ms 57 ms agg1-toronto47_xe-5-0-0_core.net.bell.ca [64.230
    .161.122]
    10 54 ms 54 ms 55 ms dis2-malton22_5-0-0.net.bell.ca [64.230.134.106]

    11 57 ms 54 ms 57 ms 67.69.228.202
    12 55 ms 54 ms 57 ms dist1-2.brm2-f2.q9.net [74.200.14.40]
    13 55 ms 54 ms 56 ms dist1-2-g-access1-2.brm2.q9.net [74.200.10.122]

    14 * * * Request timed out.
    15 * * * Request timed out.

    Tracing route to 163.6.200-74.q9.net [74.200.6.163]
    over a maximum of 30 hops:

    1 2 ms 1 ms 1 ms home [192.----]
    2 13 ms 15 ms 14 ms ---
    3 12 ms 13 ms 13 ms ----
    4 13 ms 13 ms 13 ms ---

    5 43 ms 43 ms 43 ms 151.164.99.189
    6 44 ms 45 ms 45 ms asn577-bell-ca.eqchil.sbcglobal.net [151.164.250
    .242]
    7 55 ms 57 ms 54 ms CORE1-CHICAGO23_POS1-1.net.bell.ca [64.230.186.2
    33]
    8 54 ms 55 ms 55 ms core3-toronto47_POS0-2-0-0.net.bell.ca [64.230.1
    86.125]
    9 57 ms 54 ms 54 ms agg1-toronto47_xe-5-0-0_core.net.bell.ca [64.230
    .161.122]
    10 54 ms 54 ms 54 ms dis2-malton22_5-0-0.net.bell.ca [64.230.134.106]

    11 56 ms 56 ms 54 ms 67.69.228.202
    12 55 ms 54 ms 54 ms dist1-1.brm2-f1.q9.net [74.200.14.23]
    13 56 ms 54 ms 54 ms dist1-1-g-access1-1.brm2.q9.net [74.200.10.66]
    14 * * * Request timed out.
    Tracing route to c3.b7.84ae.static.theplanet.com [174.132.183.195]
    over a maximum of 30 hops:

    1 2 ms 1 ms 1 ms home [192---]
    2 17 ms 13 ms 13 ms ---
    3 12 ms 13 ms 13 ms ---
    4 14 ms 13 ms 15 ms ---
    5 49 ms 27 ms 27 ms 151.164.101.82
    6 229 ms 224 ms 220 ms 151.164.251.162
    7 33 ms 33 ms 33 ms te6-1-10GE.ar5.DAL2.gblx.net [67.16.139.170]
    8 23 ms 23 ms 23 ms The-Planet-Dallas.TenGigabitEthernet6-2.ar5.DAL2
    .gblx.net [67.17.168.94]
    9 23 ms 23 ms 23 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

    10 23 ms 23 ms 25 ms 42.ff.5746.static.theplanet.com [70.87.255.66]
    11 22 ms 23 ms 23 ms te5-1.car13.dllstx6.theplanet.com [70.87.254.234
    ]
    12 23 ms 23 ms 23 ms c3.b7.84ae.static.theplanet.com [174.132.183.195
    ]

    Trace complete.
  • pesdcado wrote: »
    I'll do it.
    All of the tracers seems fine to me, you should try to refresh your network or try to unplug your router for one minute and replug it in. This should refresh your router.
  • C:\Documents and Settings\POP>tracert www.q9.com

    Tracing route to q9.com [216.220.36.253]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 224 ms 54 ms 151 ms 10.106.200.1
    3 111 ms 179 ms 14 ms acr01mrshtx-gbe-0-1.ftwo.tx.charter.com [96.34.1
    13.128]
    4 18 ms 139 ms 72 ms edr01ftwotx-pos-5-2.ftwo.tx.charter.com [96.34.1
    12.64]
    5 54 ms 25 ms 13 ms dtr01ftwotx-gbe-9-22.ftwo.tx.charter.com [96.34.
    112.38]
    6 118 ms 225 ms 67 ms bbr01ftwotx-tge-0-0-5-0.ftwo.tx.charter.com [96.
    34.2.32]
    7 92 ms 188 ms 118 ms so-6-0-0.edge4.Dallas1.Level3.net [4.71.216.5]
    8 180 ms 197 ms 103 ms ae-82-80.ebr2.Dallas1.Level3.net [4.69.145.179]

    9 181 ms 145 ms 196 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
    10 61 ms 151 ms 40 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
    11 305 ms 74 ms 308 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
    12 155 ms 368 ms 73 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
    13 268 ms 382 ms 60 ms ae-1-55.edge3.Chicago3.Level3.net [4.68.101.148]

    14 324 ms 348 ms 314 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
    06]
    15 363 ms 120 ms 296 ms rd1ec-ge11-0-0.il.shawcable.net [66.163.65.45]
    16 263 ms 402 ms 127 ms rc2sh-ge4-0-0.mt.shawcable.net [66.163.77.121]
    17 98 ms 257 ms 112 ms ra1fs-tge2-3.mt.shawcable.net [66.163.66.122]
    18 199 ms 266 ms 151 ms rx0sh-q9-networks.mt.bigpipeinc.com [66.244.223.
    202]
    19 58 ms 469 ms 255 ms dist1-1.tor1-f2.q9.net [69.46.123.43]
    20 361 ms 92 ms 289 ms dist1-1-g-access5-2.tor1.q9.net [69.46.121.102]

    21 330 ms 303 ms 79 ms 253.36.220-216.q9.net [216.220.36.253]

    Trace complete.
    This is what I got, thanks.