Akamai minimum prefix length issue

[hannigan at gmail.com (Martin Hannigan)]

Hi Patrick,

Correct answer. No surprise. And yes, netsupport-tix at 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 at 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 at 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 at 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
> >
> >
> >
>
>