Hi, NANOGers.
Just a quick interruption in your day to update you on the routing
fun we had. :) The problem was two-fold:
1. An errant provider router that randomly selected which
prefixes to propagate. Mix that with uRPF, and you
have FUN FUN FUN! :)
2. An interesting use
On Mon, 31 Oct 2005, Matt Taber wrote:
>
> Odd - I am seeing my route die here (from AS7949):
>
> 1 router-sf-t3sf.wmis.net (69.39.94.5) 4 msec 8 msec 4 msec
> 2 69.39.68.169 [AS 12129] 4 msec 12 msec 4 msec
> 3 edge-1.sfld-mi.123.net (216.234.96.2) [AS 12129] 4 msec 4 msec 4 msec
> 4 POS2-1.GW4.
Hi, NANOGers.
] Maybe its just _scary_ Halloween routing?
It's definitely Halloween, but this isn't as scary as it looks. :)
] 14 Cisco-Systems-1054141.cust-rtr.ameritech.net...
Back when we were part of Cisco, SBC named our link to them
accordingly. Now that we're on our own, I should prob
Hi, NANOGers.
] Unable to geto to www.cymru.com and 68.22.187.24 has been down
] for 5+ hours. Known issue?
We brought up a new BGP peer today, oddly enough to add additional
redundancy and improved performance. :) The turn-up appears to
have gone awry somewhere in the provider's network, and
On Mon, Oct 31, 2005 at 08:10:37PM +, Christopher L. Morrow wrote:
>
> On Mon, 31 Oct 2005, Roy Arends wrote:
>
> >
> > On Mon, 31 Oct 2005, matthew zeier wrote:
> >
> > > Unable to geto to www.cymru.com and 68.22.187.24 has been down for 5+
> > > hours.
> > > Known issue?
> >
> > www.cymru
Maybe its just _scary_ Halloween routing?
It works from my view of SBC/Ameritech... even though it looks like its
going through a Cisco Systems customer connection.
6 ex1-g9-0-0.pxatga.sbcglobal.net (151.164.249.9) 17.078 ms 16.964
ms 16.89
1 ms
7 bb2-p3-0.atlnga.sbcglobal.net (151.1
On Mon, 31 Oct 2005, Roy Arends wrote:
>
> On Mon, 31 Oct 2005, matthew zeier wrote:
>
> > Unable to geto to www.cymru.com and 68.22.187.24 has been down for 5+ hours.
> > Known issue?
>
> www.cymru.com resolves to 68.22.187.27 which is reachable from AS1103.
just to through more fuel on the fir
Odd - I am seeing my route die here (from AS7949):
1 router-sf-t3sf.wmis.net (69.39.94.5) 4 msec 8 msec 4 msec
2 69.39.68.169 [AS 12129] 4 msec 12 msec 4 msec
3 edge-1.sfld-mi.123.net (216.234.96.2) [AS 12129] 4 msec 4 msec 4 msec
4 POS2-1.GW4.DET5.ALTER.NET (65.206.123.245) [AS 701] 8 msec 8 ms
Getting hung up in savvis - can't ping through -
1. v140.core1.irv.intelenet.net
2. v8-ge4-1.border4.irv.intelenet.net
3. so-6-0-0.ar3.LAX1.gblx.net
4. so6-0-0-2488M.ar2.PAO2.gblx.net
5. bpr1-so-2-0-0.PaloAltoPaix.savvis.net
6. dcr2-so-3-3-0.SanFranciscosfo.savvis.net
7. dcr1-so-5-0-0.Sa
On Mon, 31 Oct 2005, matthew zeier wrote:
> Unable to geto to www.cymru.com and 68.22.187.24 has been down for 5+ hours.
> Known issue?
www.cymru.com resolves to 68.22.187.27 which is reachable from AS1103.
Roy
On Monday, 31-October-2005 13:46, matthew zeier wrote:
> Unable to geto to www.cymru.com and 68.22.187.24 has been down for
> 5+ hours. Known issue?
I think Ameritech/SBC/AT&T has problems here in Chicago. We have had
problems getting to several sites here. Traces across Ameritech's
network di
Unable to geto to www.cymru.com and 68.22.187.24 has been down for 5+ hours.
Known issue?
12 matches
Mail list logo