[117176] in North American Network Operators' Group
Re: 83.222.0.0/19 Unroutable on Verizon
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Thu Sep 3 17:27:47 2009
In-Reply-To: <alpine.BSF.2.00.0909031709580.85863@nog.angryox.com>
Date: Thu, 3 Sep 2009 17:27:19 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Peter Beckman <beckman@angryox.com>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Sep 3, 2009 at 5:20 PM, Peter Beckman<beckman@angryox.com> wrote:
> I can't reach 83.222.0.0/19 from Verizon, but I can via Cox Communication=
s
> Business Fiber as well as Level3. =A0Dies at a peering point it seems:
>
> HOST: home =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Loss% =A0 Snt =
=A0 Last =A0 Avg =A0Best =A0Wrst StDev
> =A01. mph =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0.0% =A0 =
=A020 =A0 =A00.7 =A0 0.6 =A0 0.5 =A0 0.7 =A0 0.1
> =A02. 10.1.41.89 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00.0% =A0 =A020 =
=A0 =A02.3 =A0 3.6 =A0 1.7 =A026.4 =A0 5.6
> =A03. G2-0-3-891.WASHDC-LCR-08.ver =A00.0% =A0 =A020 =A0 =A02.1 =A0 1.9 =
=A0 1.6 =A0 2.2 =A0 0.2
> =A04. so-1-1-0-0.RES-BB-RTR2.veriz =A00.0% =A0 =A020 =A0 =A02.3 =A0 2.4 =
=A0 2.2 =A0 2.8 =A0 0.1
> =A05. 0.so-6-1-0.XL4.IAD8.ALTER.NE =A00.0% =A0 =A020 =A0 =A02.8 =A0 2.8 =
=A0 2.6 =A0 3.0 =A0 0.1
> =A06. 0.xe-8-1-0.BR1.IAD8.ALTER.NE =A00.0% =A0 =A020 =A0 =A05.1 =A0 8.4 =
=A0 3.0 =A040.3 =A0 9.4
> =A07. 64.212.107.157 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00.0% =A0 =A020 =A0203=
.2 =A014.0 =A0 3.0 203.2 =A044.6
> =A08. ??? =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0100.0 =A0 =
=A020 =A0 =A00.0 =A0 0.0 =A0 0.0 =A0 0.0 =A0 0.0
it's actually being handed off to the next provider... so, maybe this
thread is mis-named? this looks like GBLX route filtering or traffic
filtering. From twtelecom I see this die inside 'retn.net' 111ms from
ashburn-ish. (so, in emea somewhere)
-chris
>
> Hop 7 alternates between 64.212.107.157 (GBLX) and 204.255.169.202 (MCI d=
ba
> Verizon) and dies after that. 83.222.32.0/19 seems to route correctly.
>
> Can anyone else confirm? =A0Bad BGP Announcement?
>
> Beckman
> -------------------------------------------------------------------------=
--
> Peter Beckman =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Internet Guy
> beckman@angryox.com =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 http://www.angryox.com/
> -------------------------------------------------------------------------=
--
>
>
