6bone stats and tools webpage links cleanup

[Peter Bunclark]

On Thu, 8 Mar 2001, William F. Maton wrote:

> On Thu, 8 Mar 2001, Warren Matthews wrote:
> 
> > I see the packet loss between SLAC and Cambridge deteriorated from a few
> > percent to up to 30% on Tuesday March 6, and there have been round trip
> > times up to 500ms whereas in February the average was around 210ms.
> > 
> > I also note no other end-node exhibits a similar pattern (although my sample
> > is very small), but a previous problem between SLAC and CRC was resolved
> > around that time. Someone in Europe (I don't recall who) was advertising
> > CRCs AS back to ESnet (SLACs provider). Probably a co-incidence.
> 
> Hmmmm....that may have been Berkom, via their v6 upstream (can't recall
> which that was).  We're still experiencing something odd with my route
> (traceroute 2001:410:401:b::2 to find out) though, and I'm now trying to
> track it down.
> 

Thanks to everyone for the various replies regarding this problem.
This morning, magically, things seem more or less back to normal.  Has
someone out there fixed something in the last 14 hours? (Certainly wasn't
a local change!)
Cheers,
	Pete.

> traceroute www.6bone.net
traceroute to 6bone.net (3ffe:b00:c18:1::10), 30 hops max, 60 byte packets
 1  cadsa (3ffe:2101:8:0:280:d8ff:fe10:51f3)  0.956 ms  0.709 ms  0.720 ms
 2  3ffe:2100:1:15::c13f:5e06  6.649 ms *  6.648 ms
 3  3ffe:1100:0:1c01::1  16.551 ms *  15.872 ms
 4  pao-6r1-if.6r1.doc.london.ip6.pipex.net (2001:600:4:4::1)  178.257 ms
*  177.598 ms
 5  3ffe:401:0:1::20:2  239.310 ms  240.985 ms  238.853 ms
 6  viagenie.ipv6.wilbury.sk (3ffe:80e1:8000::d)  367.617 ms  364.657 ms
375.976 ms
 7  www.6bone.net (3ffe:b00:c18:1::10)  380.232 ms  378.312 ms  376.369 ms