How come my traceroutes are petering out?

Discussion in 'OT Technology' started by Euclid, Jan 11, 2007.

  1. Euclid

    Euclid New Member

    Joined:
    Apr 19, 2004
    Messages:
    8,139
    Likes Received:
    0
    Location:
    Nashville, TN
    My internets are slow. We have Time Warner roadrunner (although they are transferring us to Comcast right now). I think this nationwide shuffling of cable markets is a huge clusterfuck. Anyway, can anyone help me interpret these traceroutes?

    batz:~ cmeador$ traceroute www.google.com
    traceroute: Warning: www.google.com has multiple addresses; using 64.233.167.147
    traceroute to www.l.google.com (64.233.167.147), 64 hops max, 40 byte packets
    1 192.168.0.1 (192.168.0.1) 1.048 ms 0.755 ms 0.649 ms
    2 10.59.32.1 (10.59.32.1) 8.477 ms 9.815 ms 6.455 ms
    3 srp15-0.mmphtnab-rtr2.midsouth.rr.com (24.92.64.66) 7.921 ms 7.638 ms 8.416 ms
    4 so-2-0-3-0.gar2.atlanta1.level3.net (4.78.214.13) 37.083 ms 38.022 ms 35.283 ms
    5 * ae-32-54.ebr2.atlanta2.level3.net (4.68.103.126) 35.371 ms *
    6 * * *
    7 * * *
    8 ae-21-54.car1.chicago1.level3.net (4.68.101.98) 55.504 ms ae-21-56.car1.chicago1.level3.net (4.68.101.162) 48.701 ms ae-21-52.car1.chicago1.level3.net (4.68.101.34) 49.223 ms
    9 google-inc.car1.chicago1.level3.net (4.79.208.18) 48.460 ms 72.14.232.53 (72.14.232.53) 49.808 ms 50.106 ms
    10 72.14.232.70 (72.14.232.70) 58.951 ms 64.233.175.26 (64.233.175.26) 60.949 ms 72.14.232.53 (72.14.232.53) 49.426 ms
    11 72.14.232.70 (72.14.232.70) 61.860 ms 64.233.175.26 (64.233.175.26) 61.235 ms 72.14.232.70 (72.14.232.70) 67.665 ms
    12 py-in-f147.google.com (64.233.167.147) 51.278 ms 49.448 ms 59.722 ms
    batz:~ cmeador$


    batz:~ cmeador$ traceroute www.yahoo.com
    traceroute to www.yahoo-ht2.akadns.net (69.147.114.210), 64 hops max, 40 byte packets
    1 192.168.0.1 (192.168.0.1) 1.024 ms 0.672 ms 0.647 ms
    2 10.59.32.1 (10.59.32.1) 7.229 ms 6.604 ms 7.745 ms
    3 srp15-0.mmphtnab-rtr1.midsouth.rr.com (24.92.64.65) 8.338 ms 7.556 ms 6.740 ms
    4 pos1-0.mmphtnab-rtr2.midsouth.rr.com (24.92.65.6) 7.315 ms 7.928 ms 8.711 ms
    5 so-3-0-3-0.gar2.atlanta1.level3.net (4.78.214.9) 27.340 ms 37.057 ms 26.754 ms
    6 ae-1-53.bbr1.atlanta1.level3.net (4.68.103.65) 19.803 ms ae-1-55.bbr1.atlanta1.level3.net (4.68.103.129) 30.416 ms 29.690 ms
    7 as-2-0.bbr2.sanjose1.level3.net (4.68.128.157) 100.047 ms ae-0-0.bbr1.sanjose1.level3.net (64.159.1.129) 97.926 ms as-2-0.bbr2.sanjose1.level3.net (4.68.128.157) 80.975 ms
    8 ae-13-53.car3.sanjose1.level3.net (4.68.123.77) 84.949 ms ae-23-54.car3.sanjose1.level3.net (4.68.123.109) 80.930 ms ae-13-55.car3.sanjose1.level3.net (4.68.123.141) 82.460 ms
    9 4.71.112.14 (4.71.112.14) 81.335 ms 81.531 ms 83.790 ms
    10 so-0-0-0.pat2.dcp.yahoo.com (216.115.101.150) 106.740 ms 104.367 ms 103.771 ms
    11 ge-2-1-0-p161.msr1.re1.yahoo.com (216.115.108.27) 111.021 ms ge-3-1-0-p161.msr1.re1.yahoo.com (216.115.108.67) 105.079 ms ge-2-1-0-p161.msr1.re1.yahoo.com (216.115.108.27) 105.919 ms
    12 ge-1-32.bas-a2.re3.yahoo.com (66.196.112.39) 106.594 ms ge-1-30.bas-a1.re3.yahoo.com (66.196.112.33) 95.782 ms ge-1-32.bas-a1.re3.yahoo.com (66.196.112.35) 96.401 ms
    13 * * *
    14 * * *
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    killed after 34 :hsugh:


    batz:~ cmeador$ traceroute www.netflix.com
    traceroute to www.netflix.com (216.35.131.200), 64 hops max, 40 byte packets
    1 192.168.0.1 (192.168.0.1) 2.094 ms 0.672 ms 1.503 ms
    2 10.59.32.1 (10.59.32.1) 6.583 ms 8.148 ms 7.851 ms
    3 srp15-0.mmphtnab-rtr2.midsouth.rr.com (24.92.64.66) 12.566 ms 7.569 ms 6.661 ms
    4 so-3-0-3-0.gar2.atlanta1.level3.net (4.78.214.9) 26.605 ms 27.417 ms 27.656 ms
    5 ae-1-51.bbr1.atlanta1.level3.net (4.68.103.1) 21.949 ms ae-1-55.bbr1.atlanta1.level3.net (4.68.103.129) 28.328 ms ae-1-51.bbr1.atlanta1.level3.net (4.68.103.1) 19.593 ms
    6 ae-2-0.bbr1.washington1.level3.net (4.68.128.201) 32.829 ms ae-0-0.bbr2.washington1.level3.net (4.68.128.210) 33.852 ms 33.631 ms
    7 * ae-23-52.car3.washington1.level3.net (4.68.121.48) 43.060 ms *
    8 savvis-level3-te.washington1.level3.net (4.68.110.102) 33.553 ms 34.977 ms 32.321 ms
    9 cpr1-ge-4-0-0.virginiaequinix.savvis.net (204.70.193.5) 34.495 ms 35.274 ms 36.928 ms
    10 bcs1-so-3-1-0.washington.savvis.net (208.173.10.202) 34.966 ms 34.012 ms 34.302 ms
    11 dcr1-so-0-3-0.chicago.savvis.net (204.70.192.26) 55.334 ms dcr1-so-3-0-0.atlanta.savvis.net (204.70.192.53) 73.875 ms dcr1-so-0-3-0.chicago.savvis.net (204.70.192.26) 52.827 ms
    12 dcr2-so-2-0-0.denver.savvis.net (204.70.192.133) 69.380 ms dcr1-as1.dallas.savvis.net (204.70.194.178) 54.238 ms dcr2-so-2-0-0.denver.savvis.net (204.70.192.133) 68.742 ms
    13 dcr2-so-2-0-0.losangeles.savvis.net (204.70.192.86) 88.015 ms 94.210 ms dcr1-so-2-0-0.sanfranciscosfo.savvis.net (204.70.192.114) 98.623 ms
    14 dcr1-as0-0.losangeles.savvis.net (204.70.192.117) 97.434 ms bhr1-pos-13-0.santaclarasc5.savvis.net (208.172.147.110) 100.608 ms 103.668 ms
    15 dcr2-so-2-0-0.sanfranciscosfo.savvis.net (204.70.192.90) 104.757 ms 216.34.2.226 (216.34.2.226) 99.909 ms dcr2-so-2-0-0.sanfranciscosfo.savvis.net (204.70.192.90) 111.370 ms
    16 bhr1-pos-13-0.santaclarasc4.savvis.net (208.172.147.106) 96.136 ms 216.35.133.2 (216.35.133.2) 100.984 ms bhr1-pos-13-0.santaclarasc4.savvis.net (208.172.147.106) 96.981 ms
    17 * * csr1.sc4.savvis.net (216.34.2.235) 97.885 ms
    18 * 216.35.133.2 (216.35.133.2) 97.085 ms *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    killed after 36 :hsugh:



    What's wrong? :sadwavey:
     
  2. Sexual Vanilla

    Sexual Vanilla New Member

    Joined:
    May 23, 2005
    Messages:
    6,305
    Likes Received:
    0
    Location:
    South Carolina
    Are you still able to simply ping the sites that you are tracing to? If so, that means your packet is still arriving at the intended destination. Occasionally, an * does not necessarily mean anything is wrong regarding the trace route command.

    "An asterisk, "*", followed by the words "request timed out" is not out of the ordinary. If the tracert had stopped here and continued to respond with "request timed out", then it might have been indicative of a problem. In the above example, the first "request timed out" is where the interface between our network and the rest of the Internet lies. The asterisk "*" is a normal consequence of our security implementation on that junction."

    http://www.wurd.com/misc_tracert.php
     

Share This Page