[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Akamai minimum prefix length issue
- Subject: Akamai minimum prefix length issue
- From: patrick at ianai.net (Patrick W. Gilmore)
- Date: Wed, 13 May 2015 15:37:08 -0400
- In-reply-to: <[email protected]>
- References: <[email protected]>
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
>
>
>