nanog mailing list archives
Re: Akamai minimum prefix length issue
From: "Patrick W. Gilmore" <patrick () ianai net>
Date: Wed, 13 May 2015 15:37:08 -0400
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
Current thread:
- Akamai minimum prefix length issue Chuck Church (May 13)
- Re: Akamai minimum prefix length issue Patrick W. Gilmore (May 13)
- Re: Akamai minimum prefix length issue Martin Hannigan (May 13)
- Re: Akamai minimum prefix length issue Jake Mertel (May 13)
- Re: Akamai minimum prefix length issue Patrick W. Gilmore (May 13)
- Re: Akamai minimum prefix length issue Patrick W. Gilmore (May 13)
