> > > But as I said those are 2nd in some cases 3rd hand rumours, so it could
> > > be all lies.
> >
> > I've done checks with a tool called "MTR" (Matts Traceroute). It does a
> > traceroute and then pings each hop along the trace.
> >
> > The problem starts immediately after my DSL router.
> >
> > Experiencing it again this evening quite badly ...
> >
> > Mark.
>
> Mine seems to be within Global Gateway...
>
> 5 ge-0-3-0-6.akbr3.global-gateway.net.nz 40.894 ms
> 6 p1-3.sjbr1.global-gateway.net.nz 167.555 ms
> 7 so2-1-0.pabr3.global-gateway.net.nz 200.380 ms
>

Fran,

You got a 40ms ping off a network device located in Aucklnad.
It then went up by 120ms or so. Assuming that is infact San Jose, CA (and
its hard to tell as the IP is an APNIC issue, you cant rely on the dns
name... but its a fair guess) then youre traversing Southern Cross
(admin'd by Telecom, so the ip issue makes sense as they administer it)
and youre going to gain about 120ms minimum over that hop anyway.

eg, the sample traceroute you quote isnt particularly bad.

Let me show you something illustrative:

 1 dsl500 (192.168.2.254) 1.271 ms 1.287 ms 0.955 ms
 2 222-153-0-1.jetstream.xtra.co.nz (222.153.0.1) 1816.298 ms 1773.896
ms 1589.640 ms
 3 222.152.127.189 (222.152.127.189) 2155.690 ms 1838.041 ms 2062.902
ms
 4 202.50.245.190 (202.50.245.190) 2018.646 ms 2595.093 ms 1965.239 ms

Now _That_ is the kind of performance hit i'm talking about... |

Mark.

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message