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

Philipp Kern phil at
Mon Aug 20 18:41:36 CEST 2012


am Mon, Aug 20, 2012 at 06:17:24PM +0200 hast du folgendes geschrieben:
> In reference to
> In other words it makes things "sometimesnot work"....
> Announcing /48s will get filtered and this randomly breaks stuff.

r-ir-cs-1#show bgp ipv6 unicast 2a02:26f0::/32  
BGP routing table entry for 2A02:26F0::/32, version 2801974
Paths: (2 available, best #1, table Default)
  Advertised to update-groups:
  553 3549 4436 34164 34164
    2001:7C0:3:702:: (FE80::4255:39FF:FE3A:60C3) from 2001:7C0:3:702:: (
      Origin IGP, metric 50, localpref 100, valid, external, best
      Community: 553:304 3549:4405 3549:30840 4436:42532
  553 3549 4436 34164 34164
    2001:7C0:3:703:: (FE80::FA66:F2FF:FE11:8E72) from 2001:7C0:3:703:: (
      Origin IGP, metric 200, localpref 100, valid, external
      Community: 553:304 3549:4405 3549:30840 4436:42532

I do see the covering aggregate and in [1] to which you answered an Akamai
employee said that it's supposed to be announced. What's the problem with those
more specific? Aren't they reachable through the covering aggregate, too?
(I cannot test because my peers accept the specifics.)

Also I see a route6 for instance for 2a02:26f0:0005::/48:

route6:         2a02:26f0:0005::/48
descr:          Akamai Technologies
origin:         AS20940
notify:         ip-admin at
mnt-by:         AKAM1-RIPE-MNT
changed:        ck at 20101220
source:         RIPE

Kind regards
Philipp Kern

[1] <FECAD2E8-7A8E-4A9A-A5C6-98551D30E0C8 at>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : 

More information about the ipv6-ops mailing list