nanog mailing list archives
Re: www.google.com latency/packet loss/very slow thru savvis
From: "Christopher L. Morrow" <christopher.morrow () mci com>
Date: Tue, 13 Dec 2005 22:23:09 +0000 (GMT)
On Tue, 13 Dec 2005, Richard A Steenbergen wrote:
Oh and FYI it is still going on, though the route just changed 4 mins ago: [BGP/170] 00:04:21, localpref 200 AS path: 7473 17557 17557 17557 17557 5400 15169 I Singtel -> Pakistan Telecom -> British Telecom -> Google. AS17557 is leaking its BGP table, and AS7473 is not filtering its customer. Bad network, bad. No cookie.
and... sbgp would have fixed this for us! :) Seriously though, in the last 12 months there have been atleast 4 major route leaks like this, eh? Is the lesson not being learned to filter custoemrs?
Current thread:
- www.google.com latency/packet loss/very slow thru savvis Erik Sundberg (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Chris Stone (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Mark Foster (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Bill Sehmel (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Richard A Steenbergen (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Richard A Steenbergen (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Christopher L. Morrow (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis william(at)elan.net (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Richard A Steenbergen (Dec 13)
- Re: www.google.com latency/packet loss/very slow thru savvis Chris Stone (Dec 13)