[194403] in North American Network Operators' Group
Re: ATT (AS7018) cannot reach AS31334
daemon@ATHENA.MIT.EDU (Nimrod Levy)
Tue Apr 18 10:50:25 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <20170414180352.GA81567@c67c3dd65f017f13199878a6cf05e232bc4d0f5eb07f34f7>
From: Nimrod Levy <nimrodl@gmail.com>
Date: Mon, 17 Apr 2017 19:41:09 +0000
To: David Hill <dhill+nanog@mindcry.org>, nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
From what I can see, 31334 is sending prefixes covering this IP to
upstreams 1273 and 6939 (possibly others, but that's what I saw). Neither
of these networks propagate those prefixes into 7018 directly or indirectly
so we have no path to get there. I would encourage 31334 to check with
their upstreams to understand why the routes don't get sent to 7018.
--
Nimrod
On Mon, Apr 17, 2017 at 10:28 AM David Hill <dhill+nanog@mindcry.org> wrote:
> Hi -
>
> I am a ATT customer unable to reach AS31334. Is anyone on this list
> able to check into this? It works from non-ATT route-servers I have
> tested on.
>
> ATT route-server
> ----------------
> rviews@route-server.ip.att.net> ping 2a02:8100:4:2::156e count 3
> PING6(56=40+8+8 bytes) 2001:1890:111d:1::28 --> 2a02:8100:4:2::156e
>
> --- 2a02:8100:4:2::156e ping6 statistics ---
> 3 packets transmitted, 0 packets received, 100% packet loss
>
> Thank you,
> David
>
--
--
Nimrod
