1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Trace Evalution

Discussion in 'Bits & Bytes' started by ethics, Nov 25, 2002.

  1. ethics

    ethics Pomp-Dumpster Staff Member

    Trace Evaluation

    Couldn't access the forum for a bit, but running trace route produced the following:

    TraceRoute to 66.227.76.55 [globalaffairs.org]

    Hop (ms) (ms) (ms) IP Address Host name
    1 0 0 16 66.46.176.3 -
    2 0 0 0 216.191.97.45 pos5-2.core2-mtl.bb.attcanada.ca
    3 0 0 0 216.191.65.217 srp2-0.core1-mtl.bb.attcanada.ca
    4 16 0 0 216.191.65.173 pos8-1.core2-tor.bb.attcanada.ca
    5 15 0 16 216.191.65.243 srp2-0.gwy1-tor.bb.attcanada.ca
    6 15 16 15 12.125.142.5 -
    7 16 15 16 12.123.5.222 gbr6-p80.cgcil.ip.att.net
    8 Timed out Timed out Timed out -
    9 16 16 31 12.123.6.37 -
    10 16 15 16 209.0.227.77 so-1-1-0.edge1.chicago1.level3.net
    11 15 31 16 209.244.8.13 so-7-0-0.mp2.chicago1.level3.net
    12 63 62 63 209.247.11.169 so-0-2-0.mp1.houston1.level3.net
    13 47 63 47 209.247.11.182 gige9-0.hsipaccess1.houston1.level3.net
    14 47 63 62 209.247.121.218 unknown.level3.net
    15 62 47 63 66.7.143.178 o0-2jp1.hou002bd01.yipes.com
    16 63 47 62 66.7.143.165 o0-2bd1.hou002bd02.yipes.com
    17 47 62 63 66.7.143.158 o0-2bd2.hou003bd02.yipes.com
    18 62 47 63 66.7.143.54 o5-3bd2.hou005ap01.yipes.com
    19 62 63 47 66.54.158.66 summittrading.com
    20 47 78 63 66.227.76.55 -

    Trace complete

    Is it safe to assume that it was the 8th hop and not the server itself?
     
  2. ethics

    ethics Pomp-Dumpster Staff Member

    But re-running this trace, I get the same thing while the forum is up?

    Unless time outs are set to something like 500 ms...

    Anyway, submitted a trouble ticket AGAIN.
     
  3. mikeky

    mikeky Member

    I did a trace route from here when the site was down and didn't see any major problems with the routing, leading me to think it's the server.
     
  4. ethics

    ethics Pomp-Dumpster Staff Member

    Will post here what the ISP says. Thanks Mike.
     
  5. midranger4

    midranger4 Banned

    Hop 8 is refusing pings Ethics.

    Refusing pings is a more and more common practice used by various internet service providers these days.

    I'm a Comcast HSI subscriber and Comcast refuses all pings internal to their network. Any traceroute I do the first four hops or so do not return pings. Once my packets are handed off to the level 3 backbone then I can see the pings.

    This is done by ISP's for a variety of reasons. One could argue that by refusing pings the target is in fact conserving bandwith. The more common mindset (from a customer perspective) is that by refusing pings the provider can conceal a performance problem, making it that much more difficult to isolate a potential botteleneck.

    Let's take your trace as an example. If hop 9 was returning 400ms pings you might assume it was the problem right? Well what about hop 8? Maybe its the culprit only youcan't see the pings therefore your unable to determine with complete accuracy where the problem lies. You would have to say the problem is either hop 8 OR hop 9.
     
  6. ethics

    ethics Pomp-Dumpster Staff Member

    Thanks Mid. Learning more from you guys than you can imagine. I feel spongy. :)
     
  7. midranger4

    midranger4 Banned

    sample

    Here's a sample trace to globalaffairs from my house.

    Notice the first hops are concealed?

    If I were to ping another comcast subscriber the final hops would be concealed as well.
     

Share This Page