Routing problems to 2400:CB00::/32 CLOUDFLARE

Bernhard Schmidt berni at
Sat Jun 16 15:45:41 CEST 2012

On 16.06.2012 15:00, Laurent GUERBY wrote:


> Our experience operating a /40 PA from RIPE is that a very low number of
> AS filter at /32 on RIPE PA space and thus do not follow RIPE-532: based
> on our users feedback we found only 3, one of which has announced it
> will try to follow RIPE-532 in the future.

You might just not see the problem, because (as opposed to the 
Cloudflare case) your /32 aggregate IS announced. Traffic will go out of 
filtering ISPs and either hit the /40 more-specific somewhere or go on 
down the /32 route.

csr1-0q1#sh bgp ipv6 2a01:6600::/32 long
    Network          Next Hop            Metric LocPrf Weight Path
*>i2A01:6600::/32   2001:4CA0::5             0    100      0 680 3356 
174 39405 i
* i                 2001:4CA0::5             0    100      0 680 3356 
174 39405 i
% NOTE: This command is deprecated. Please use 'show bgp ipv6 unicast'

Yes, my network does not accept /40s from PA.

Best Regards,

More information about the ipv6-ops mailing list