[179925] in North American Network Operators' Group
Re: Akamai minimum prefix length issue
daemon@ATHENA.MIT.EDU (Martin Hannigan)
Wed May 13 18:33:36 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <7948BDB7-C04C-4D3B-A7E5-B59EDCC9F391@ianai.net>
From: Martin Hannigan <hannigan@gmail.com>
Date: Wed, 13 May 2015 18:32:49 -0400
To: "Patrick W. Gilmore" <patrick@ianai.net>,
Chuck Church <chuckchurch@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Hi Patrick,
Correct answer. No surprise. And yes, netsupport-tix@akamai.com is still
the way to go for these types of issues.
Thanks for the help!
Best,
-M< // AS 20940
On Wed, May 13, 2015 at 3:37 PM, Patrick W. Gilmore <patrick@ianai.net>
wrote:
> Akamai does not follow BGP perfectly, for many reasons, including BGP
> preferring crappy paths much of the time.
>
> ISPs should email NetSupport-tix@akamai.com to get help with traffic
> engineering, performance, and other questions. (Or at least that used to be
> the case a year ago.)
>
> --
> TTFN,
> patrick
>
> > On May 13, 2015, at 15:33 , Chuck Church <chuckchurch@gmail.com> wrote:
> >
> > Anyone from Akamai (or who might know),
> >
> > Having an issue with AS 20940 either not seeing or ignoring a /23
> > we're announcing, and following a /22 to another path. Other ISPs our
> > upstream peers with see the /23. I didn't see a looking glass for
> Akamai to
> > verify. Anyone from Akamai able to help? Prefix in question is
> > 162.220.232.0/23.
> >
> > Thanks,
> >
> > Chuck
> >
> >
> >
>
>
