ntacpeering - Re: Akamai Routes on TR-CPS
Subject: NTAC Peering Working Group
List archive
- From: John Hernandez <>
- To: Michael H Lambert <>
- Cc:
- Subject: Re: Akamai Routes on TR-CPS
- Date: Wed, 19 Sep 2012 15:55:54 -0600
Apple's iOS update got you poking around? Our Akamai farm's traffic spiked
by ~ 2.5 Gb/s (more than doubled) at release time, and it's still way up
there.
Back to your question though, supposing one of those (roughly 350) server
farms is chosen by Akamai DNS-foo to serve us content, I don't see why TR/CPS
would be a bad choice for pushing ACK's, regardless of which path the bulk
data takes.
On Sep 19, 2012, at 3:26 PM, Michael H Lambert wrote:
> In looking at the TR-CPS routing table, I see a number of routes with 20940
> (Akamai) in the AS path. The vast majority of these are NOT "^11164 20940
> .*". I can't imagine that these other destinations would serve content to
> random sources in our community, so is there any reason that they should be
> accepted into the routing table? I could imagine their presence leading to
> some weird return paths. I'm assuming that "^11164 20940$" would work as
> expected.
>
> Michael
>
--
John Hernandez, Network Engineer
1850 Table Mesa Drive, Boulder, CO 80305
Tel. 303-497-1280 Fax. 303-497-1818
- Akamai Routes on TR-CPS, Michael H Lambert, 09/19/2012
- Re: Akamai Routes on TR-CPS, John Hernandez, 09/19/2012
- Re: Akamai Routes on TR-CPS, Darrell Newcomb, 09/19/2012
- Re: Akamai Routes on TR-CPS, David Farmer, 09/19/2012
- Re: Akamai Routes on TR-CPS, Darrell Newcomb, 09/19/2012
- Re: Akamai Routes on TR-CPS, Michael H Lambert, 09/19/2012
- Re: Akamai Routes on TR-CPS, David Farmer, 09/19/2012
Archive powered by MHonArc 2.6.16.