83.222.0.0/19 Unroutable on Verizon

Christopher Morrow morrowc.lists at gmail.com
Thu Sep 3 21:27:19 UTC 2009


On Thu, Sep 3, 2009 at 5:20 PM, Peter Beckman<beckman at angryox.com> wrote:
> I can't reach 83.222.0.0/19 from Verizon, but I can via Cox Communications
> Business Fiber as well as Level3.  Dies at a peering point it seems:
>
> HOST: home                        Loss%   Snt   Last   Avg  Best  Wrst StDev
>  1. mph                           0.0%    20    0.7   0.6   0.5   0.7   0.1
>  2. 10.1.41.89                    0.0%    20    2.3   3.6   1.7  26.4   5.6
>  3. G2-0-3-891.WASHDC-LCR-08.ver  0.0%    20    2.1   1.9   1.6   2.2   0.2
>  4. so-1-1-0-0.RES-BB-RTR2.veriz  0.0%    20    2.3   2.4   2.2   2.8   0.1
>  5. 0.so-6-1-0.XL4.IAD8.ALTER.NE  0.0%    20    2.8   2.8   2.6   3.0   0.1
>  6. 0.xe-8-1-0.BR1.IAD8.ALTER.NE  0.0%    20    5.1   8.4   3.0  40.3   9.4
>  7. 64.212.107.157                0.0%    20  203.2  14.0   3.0 203.2  44.6
>  8. ???                          100.0    20    0.0   0.0   0.0   0.0   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 dba
> Verizon) and dies after that. 83.222.32.0/19 seems to route correctly.
>
> Can anyone else confirm?  Bad BGP Announcement?
>
> Beckman
> ---------------------------------------------------------------------------
> Peter Beckman                                                  Internet Guy
> beckman at angryox.com                                 http://www.angryox.com/
> ---------------------------------------------------------------------------
>
>




More information about the NANOG mailing list