02-Jan-03 at 12:36, Bill James (billibill.no-ip.org) wrote :
> Here is a trace from the far side of my cable modem...Times are VERY high
> once you get close to you
> 24 202.41.225.34 (202.41.225.34) 500.919 ms 502.656 ms 500.510 ms

Call 500ms high? Obviously never been the wrong side of a satellite link
then. A lot of places in Africa I've been to don't get less than about
800ms to anywhere.

DNS lookups are working here now. They'll be cached for the TTL value so
clearly that should be OK.

I think this is probably a transitory problem, maybe a DNS not
responding for a while, or some cache pollution somewhere due to a bad
entry.

A few hops from a trace from here:-

12 202.183.72.182 (202.183.72.182) 456.167 ms 463.511 ms 462.259 ms
13 202.41.225.34 (202.41.225.34) 607.545 ms 600.297 ms 611.907 ms
14 unassigned-31-66-109-203.worldgatein.com (203.109.66.31) 485.743 ms
490.235 ms 483.796 ms
15 mx1.worldgate.co.in (203.109.64.24) 458.024 ms 547.959 ms 464.095
ms

Seems that there may be congestion upstream though, since there's a lot
of variance in times between two packets

From a ping summary:
22 packets transmitted, 21 packets received, 4% packet loss
round-trip min/avg/max/mdev = 451.829/456.372/471.314/5.163 ms

So there may be a bit of packet loss / congestion... is your link
saturated upstream?

-- 
[Simon White. vim/mutt. simonmtds.com. Foldinghome no log script yet...]
It is impossible to sharpen a pencil with a blunt axe. It is equally vain
to try to do it with ten blunt axes instead.  -- E. W. Dijkstra
[Linux user #170823 http://counter.li.org. Home cooked signature rotator.]

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]