[194175] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Facebook more specific via Level3 ?

daemon@ATHENA.MIT.EDU (Jay Nakamura)
Tue Mar 21 13:37:33 2017

X-Original-To: nanog@nanog.org
In-Reply-To: <01dd01d2a264$17d91e20$478b5a60$@jaritsch.at>
From: Jay Nakamura <zeusdadog@gmail.com>
Date: Tue, 21 Mar 2017 13:37:28 -0400
To: =?UTF-8?Q?J=C3=BCrgen_Jaritsch?= <juergen@jaritsch.at>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

I see that specific route both of my upstreams and not going through level
3.

    Network            Next Hop        MED    LocPrf     Weight Path
*>x 31.13.70.0/24      x.x.x.x 0          80         0      6461 32934 i
*i  31.13.70.0/24      x.x.x.x 0          80         0      209 32934 i
*   31.13.70.0/24      x.x.x.x   10         80         0      209 32934 i


On Tue, Mar 21, 2017 at 12:56 PM, J=C3=BCrgen Jaritsch <juergen@jaritsch.at=
>
wrote:

> Hi,
>
>
>
> is anyone else receiving Facebook=E2=80=99s /24 more specific from Level3=
 (AS3356)?
>
>
>
> 31.13.70.0/24      *[BGP/170] 1w5d 17:21:28, MED 0, localpref 100, from
> a.b.c.d
>
>                       AS path: 3356 32934 I, validation-state: unverified
>
>
>
> This more specific is only visible via AS3356 =E2=80=A6 Facebook isn=E2=
=80=99t even
> announcing it via direct peering.
>
>
>
> Any Facebook admin on or off list available to get this debugged and
> tracked
> down?
>
>
>
>
>
> Thanks & best regards
>
> J=C3=BCrgen
>
>

home help back first fref pref prev next nref lref last post