[179921] in North American Network Operators' Group
Re: Akamai minimum prefix length issue
daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Wed May 13 15:37:11 2015
X-Original-To: nanog@nanog.org
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <015701d08db3$ab4fcae0$01ef60a0$@gmail.com>
Date: Wed, 13 May 2015 15:37:08 -0400
To: Chuck Church <chuckchurch@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
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.)
--=20
TTFN,
patrick
> On May 13, 2015, at 15:33 , Chuck Church <chuckchurch@gmail.com> =
wrote:
>=20
> Anyone from Akamai (or who might know),
>=20
> 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.=20
>=20
> Thanks,
>=20
> Chuck
>=20
>=20
>=20
