Dear Akamai, you got a /32 there not a bunch of /48s - how to break Facebook and annoy lots of users

Nick Hilliard nick at
Mon Aug 20 22:30:31 CEST 2012

On 20/08/2012 21:07, Jeroen Massar wrote:
> And likely if you traceroute the space it is located in the same network
> as the covering prefix...

Have you looked at the entries for each of the smaller prefixes?  They go
all over the place.  And there are no covering prefixes for the PA
allocations.  The longest prefix is /20.

> But maybe it is better to have a third one which basically means that
> content-providers/CDN/etc that have a large address space can have a big
> chunk of address space and then announce more specifics.

There are sufficiently few large CDNs that this probably isn't required.

> PI's normally come in /48s and even an Akamai would likely be good with
> a /48 per location. Those 800 /48's (or heck /40s) could all come out of
> the same block, but from a larger block that is meant for it.

What you're saying here is that they should have been given space from a
different range so that you could continue with a /32 netmask filter.

RIPE-555 suggests that your netmask filter should be /48.  The days of
filtering at /32 are already over, at least in the RIPE region.  If you
continue to filter at /32, you should expect connectivity problems.


More information about the ipv6-ops mailing list