Re: squid-cache.org connectivity

From: Adrian Chadd <adrian@dont-contact.us>
Date: Wed, 29 Aug 2001 13:51:41 -0600

On Wed, Aug 29, 2001, Henrik Nordstrom wrote:
> Adrian Chadd wrote:
>
> > On Wed, Aug 29, 2001, Henrik Nordstrom wrote:
> > > Is it only me, or is there bad connectivity with squid-cache.org?
> >
> > Traceroute? :-)
>
> Thanks for the reminder.
>
> Seems to be some problem relatively close to squid-cache.org..
>
> [all fine up to here]
> 24 fa-2-1-0.a01.dnvrco01.us.ra.verio.net (129.250.53.225) 422.644 ms
> 386.779 ms 355.896 ms
> 25 d3-8-0-0.a01.dnvrco01.us.ce.verio.net (199.239.59.222) 468.713 ms
> * *
> 26 * * border3.ge2-0-bbnet.den.pnap.net (216.52.40.7) 444.111 ms
> 27 * * coop-1.border3.den.pnap.net (216.52.42.102) 395.567 ms
> 28 gw112.boulder.co.coop.net (199.45.128.13) 344.604 ms * *
> 29 border-to-279-themeasurementfact.boulder.co.coop.net
> (199.45.133.62) 410.026 ms 490.510 ms *

Jesus. 30 hops? You're lucky the traceroute even finished. :-)

Dunno. Those routers may be overloaded. THe trouble with traceroutes
is that they are generally CPU generated, and so the router could be
quite fine but the CPU could be trashed, resulting in slow routing
updated, slow ping/traceroute returns, but fine packet throughput.

Adrian (taking is routerboy hat off.)
Received on Wed Aug 29 2001 - 13:51:43 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:17 MST