Akamai does not follow BGP perfectly, for many reasons, including BGP
preferring crappy paths much of the time.
ISPs should email netsupport-...@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,
Akamai does not do this.
--
TTFN,
patrick
On May 13, 2015, at 15:42 , Jake Mertel j...@nobistech.net wrote:
Chuck,
Just throwing this out there as a possibility, I've seen similar issues
with other ISPs wherein the root cause was their BGP speaking routers using
a filter set published
Chuck,
Just throwing this out there as a possibility, I've seen similar issues
with other ISPs wherein the root cause was their BGP speaking routers using
a filter set published by (I'm almost certain) Cisco that, among other
things, blocks announcements of any prefix that is smaller then the
Hi Patrick,
Correct answer. No surprise. And yes, netsupport-...@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 patr...@ianai.net
wrote:
Akamai does not follow BGP perfectly, for
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
5 matches
Mail list logo
