erratic ping times

Discussion in 'Hardware' started by brazilianwonder, Aug 7, 2008.

  1. Does anybody know what causes these? Preliminary searches talk about an oversold node? Anymore ideas...Anything I can do to fix this from my end without going through my provider? I am using cable internet.

    Here is a test to yahoo.com from Brazil. Notice that some pings are absurdly above average when they should all be close to each other.

    Pinging yahoo.com [206.190.60.37] with 32 bytes of data:

    Reply from 206.190.60.37: bytes=32 time=238ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=158ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=158ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=157ms TTL=57

    Ping statistics for 206.190.60.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 157ms, Maximum = 238ms, Average = 177ms

    C:\Documents and Settings\Thiago>ping yahoo.com

    Pinging yahoo.com [206.190.60.37] with 32 bytes of data:

    Reply from 206.190.60.37: bytes=32 time=226ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=244ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=160ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=163ms TTL=57

    Ping statistics for 206.190.60.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 160ms, Maximum = 244ms, Average = 198ms

    C:\Documents and Settings\Thiago>ping yahoo.com

    Pinging yahoo.com [206.190.60.37] with 32 bytes of data:

    Reply from 206.190.60.37: bytes=32 time=164ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=187ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=160ms TTL=57
    Reply from 206.190.60.37: bytes=32 time=146ms TTL=57

    Ping statistics for 206.190.60.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 146ms, Maximum = 187ms, Average = 164ms

    C:\Documents and Settings\Thiago>
     
  2. GTS

    GTS

    Try running PingPlotter - you need to find out which hop(s) is causing the latency
     
  3. Yeah . . . Now go back and do a TRACERT after the DOS prompt, inputting the yahoo IP address of 206.190.60.37 and see what HOP shows where the latency is occuring.
     
  4. I agree get the free version of PingPlotter. You can get it from the bottom of his page. http://pingplotter.com/download.html

    Also, I think you will find that pinging an IP address or www address will only give you the latency from the previous hop to the address you are pinging, and not the aggregate or collective latency from your computer to the address you are pinging. You can see this when you run PingPlotter.
     
  5. paden

    paden

    great suggestions... now, if i only new what I was looking at...

    : )

    I was smart at one time.
     
  6. I have been able to identify two bad hops that are no longer being used which restored my ping times to normal. I guess I can now keep an eye on those hops in case they come back I'll know they will delay my orders.

    I used pingplotter. Thanks for the tips.
     
  7. paden

    paden

    According to TOS, if you want to test theirs, use rainbow.thinkorswim.com