Dear Akamai, you got a /32 there not a bunch of /48s - how to break Facebook and annoy lots of users
Patrick W. Gilmore
patrick at ianai.net
Tue Aug 21 07:59:15 CEST 2012
On Aug 20, 2012, at 16:07 , Jeroen Massar <jeroen at unfix.org> wrote:
> On 2012-08-20 19:45, Nick Hilliard wrote:
>> On 20/08/2012 17:42, Jeroen Massar wrote:
>>> Most of those are out of PA space that is announced inside the ISP that
>>> that prefix is living in and thus which do not need to be seen in the
>>> rest of the DFZ as they come out of a PA block.
>> 18.104.22.168/13: 53 announcements
>> 22.214.171.124/12: 110 announcements
>> 126.96.36.199/11: 170 announcements
>> 188.8.131.52/14: 54 announcements
>> etc, etc, etc. I got bored at this stage and stopped totting up their
>> larger allocations (there are lots more), but that's already nearly half
>> the space they announce. It's PA space, but all allocated to Akamai and
>> announced as smaller prefixes.
> And likely if you traceroute the space it is located in the same network
> as the covering prefix... thus why is the route there?
Let's all just assume Akamai is not completely confused or ignorant.
We announce no block unless it has multiple paths. At least not intentionally. If you believe you have found an exception to this rule, let me know.
More information about the ipv6-ops