Akamai v6 - peering issue?

[#1]

All OK for me.

[#2]

Just wondering if anyone is having issues with Akamai over v6 again? I am having issues with Facebook/Instagram images timing out again.

[#3]

can you post some direct url's here so can test?

[#4]

Try http://photos-g.ak.instagram.com/hphotos-ak-xaf1/t51.2885-15/10899153_873421292713054_1539817145_n.j...
The images are loading (eventually), but they are taking forever:



I'm on pcl-bng02 - if I disable v6, then I have no issues with any CDN hosted images.

[#5]

I put

photos-g.ak.instagram.com       2a02:26f0:c8::17c0:a2e1

in my hosts file as then able to access the image in Firefox via v6. I'm on ptw-ag03

[#6]

Does the image always load for you? Sometimes it loads for me/sometimes it doesn't.
Here's my v6 DNS lookup for that address (photos-g.ak.instagram.com):

Quote

;; ANSWER SECTION: photos-g.ak.instagram.com. 157 IN CNAME photos-g.ak.instagram.com.edgesuite.net. photos-g.ak.instagram.com.edgesuite.net. 11783 IN CNAME a1007.dspw42.akamai.net. a1007.dspw42.akamai.net. 20 IN AAAA 2a02:26f0:c8::17c0:a2e1 a1007.dspw42.akamai.net. 20 IN AAAA 2a02:26f0:c8::17c0:a2b2

[#7]

Seems to be always loading. Here's the tracert if that helps:

C:\Users\John>tracert photos-g.ak.instagram.com
Tracing route to a1007.dspw42.akamai.net [2a02:26f0:c8::17c0:a2b2]
over a maximum of 30 hops:
  1     1 ms    <1 ms    <1 ms  dsldevice.lan [2a02:16c8:*****]
  2    20 ms    17 ms    18 ms  2a02:16c8:0:1::1f
  3    17 ms    17 ms    16 ms  2a02:16c8:1:2::b
  4    17 ms    22 ms    17 ms  2a02:16c8::a
  5    19 ms    23 ms    24 ms  40ge1-3.core1.lon2.he.net [2001:7f8:4::1b1b:1]
  6    25 ms    25 ms    35 ms  100ge5-1.core1.par2.he.net [2001:470:0:2ce::2]
  7    25 ms    24 ms    25 ms  seabone-net-as6762.10gigabitethernet11-7.core1.par2.he.net [2001:470:0:2d8::2]
  8    30 ms    26 ms    25 ms  lo0.londra32.lon.seabone.net [2001:41a8:400::20]
  9    26 ms    26 ms    26 ms  2001:41a8:400:2::ce
 10    26 ms    26 ms    26 ms  2a02:26f0:c8::17c0:a2b2
Trace complete.

[#8]

Thanks
I seem to get some timeouts from the last hop which might be the cause:

Quote

$ traceroute6 -I photos-g.ak.instagram.com traceroute6: Warning: a1007.dspw42.akamai.net has multiple addresses; using 2a02:26f0:c8::17c0:a2b2 traceroute6 to a1007.dspw42.akamai.net (2a02:26f0:c8::17c0:a2b2) from 2a02:16c8:8880:1100:e0cb:393:d654:7ecd, 64 hops max, 16 byte packets 1  2a02:16c8:xx:xx::x  0.355 ms  0.369 ms  0.303 ms 2  2a02:16c8:0:1::4:10  3.718 ms  3.729 ms  3.425 ms 3  2a02:16c8:1:8310::1  3.756 ms  3.849 ms  4.032 ms 4  2a02:16c8:1:2::6  4.110 ms  4.171 ms  4.052 ms 5  40ge1-3.core1.lon2.he.net  3.961 ms  4.240 ms  4.341 ms 6  100ge5-1.core1.par2.he.net  12.266 ms  14.317 ms  12.679 ms 7  seabone-net-as6762.10gigabitethernet11-7.core1.par2.he.net  12.702 ms  12.533 ms  12.536 ms 8  lo0.londra32.lon.seabone.net  13.561 ms  13.387 ms  13.512 ms 9  2001:41a8:400:2::ce  13.261 ms  14.869 ms  14.591 ms 10  * * * 11  * * * 12  * * * 13  *    2a02:26f0:c8::17c0:a2b2  * 13.742 ms  13.590 ms

Can you try pinging the last hop (2a02:26f0:c8::17c0:a2b2) to see if you get any timeouts? I am seeing packet loss to that address for some reason:

Quote

--- 2a02:26f0:c8::17c0:a2b2 ping6 statistics --- 145 packets transmitted, 25 packets received, 82.8% packet loss round-trip min/avg/max/std-dev = 13.471/41.884/225.420/63.911 ms

[#9]

Trace working fine for me too, although it's resolving to a different IP:

C:\Windows\System32>tracert photos-g.ak.instagram.com
Tracing route to a1007.dspw42.akamai.net [2a02:26f0:b7::adde:d2db]
over a maximum of 30 hops:
  1     3 ms     3 ms     3 ms  2a02:16c8:X:X:X:X:X:X
  2    17 ms    18 ms    19 ms  2a02:16c8:0:1::1b
  3    15 ms    16 ms    16 ms  2a02:16c8:1:2::13
  4    15 ms    16 ms    15 ms  2a02:16c8::b
  5    25 ms    25 ms    24 ms  lonap.he.net [2001:7f8:17::1b1b:1]
  6    15 ms    15 ms    24 ms  10ge5-2.core1.lon2.he.net [2001:470:0:2cd::1]
  7    17 ms    16 ms    16 ms  2001:7f8:4::fb:1
  8    16 ms    16 ms    16 ms  ae0-1101.cr1.lon4.uk.ipv6.kaiaglobal.com [2a02:b0:ffff:ffff:ffff:fff
f:fffe:da]
  9    17 ms    25 ms    25 ms  akamai.cr1.lon4.uk.ipv6.kaiaglobal.com [2a02:b0:ffff:ffff:ffff:ffff:
ffff:de]
 10    16 ms    15 ms    15 ms  2a02:26f0:b7::adde:d2db
Trace complete.

Ping to 2a02:26f0:c8::17c0:a2b2, I'm seeing latency increases every minute or so:

C:\Windows\System32>ping -6 -t 2a02:26f0:c8::17c0:a2b2
Pinging 2a02:26f0:c8::17c0:a2b2 with 32 bytes of data:
Reply from 2a02:26f0:c8::17c0:a2b2: time=111ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=128ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=172ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=121ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=151ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=87ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=205ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=164ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=182ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=146ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=27ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=25ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=35ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=26ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=34ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=25ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=26ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms...
--------8<-------SNIP------8<---------
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=596ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=37ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=26ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=25ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=27ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=25ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=25ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=172ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=153ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=161ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=101ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=131ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=122ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=197ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=138ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=118ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=23ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=37ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=33ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=26ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=24ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=25ms
Reply from 2a02:26f0:c8::17c0:a2b2: time=26ms
Ping statistics for 2a02:26f0:c8::17c0:a2b2:
    Packets: Sent = 257, Received = 257, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 596ms, Average = 47ms

[#10]

Ping looks perfectly OK:

Ping statistics for 2a02:26f0:c8::17c0:a2b2:
    Packets: Sent = 126, Received = 126, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 29ms, Average = 25ms

[#11]

it loaded here but for some reason firefox is loading it over ipv4, suggesting the ipv6 ip had an issue.

[#12]

When I first tried it loaded over IPv4 so I added the entry to hosts to force IPv6.

[#13]

From what I can tell, it loaded over IPv6 for me without any hosts file trickery:

[#14]

Changing gateways seems to have fixed it (tried pcl-bng01 and ptw-bng02 without issue). When I changed to pcl-bng02, it re-occured though.
@ Bob - Did you ever find out what the cause of this was here http://community.plus.net/forum/index.php/topic,126633.msg1116201.html#msg1116201 ? I think the problems are identical. I believe in the past that it was fixed by Paul (http://community.plus.net/forum/index.php/topic,126633.msg1100272.html#msg1100272).
Edit: I spoke too soon. Some akamaihd.net images/scripts are just pending again and not loading on both Facebook and Instagram.

[#15]

now its loading ipv6, no issues.