<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Akamai v6 - peering issue? in IPv6 Trial</title>
    <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094560#M2280</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote from: AndyH&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;BR /&gt;I've been running an MTU of 1500 for a little while now without any problems, although I have had issues in the past. At the moment, I can send a do-not-fragment 1500 bytes packet from an outside server to my home Mac without any issues.&lt;BR /&gt;There does seem to be a difference between the setup on the BNGs vs the older AGs. As far as I can see, the BNGs seem happier to handle an MTU &amp;gt; 1492 for IPv6 than the AGs. However, there seems to be something amiss with Akamai when I have a 1500 MTU on a BNG.&lt;BR /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;Interesting - whats the MTU on your pppoe link? Generally it should be no more than 1492 as PPP adds 8 bytes of header and it is then itself carried over 1500byte ethernet presented at the CPE modem - so if you have a 1500 MTU at the TCP layer then problems start cropping up, especially with ipv6. Ipv4 will likely mask the issues due to fragmentation happening at hops. Of course, if the upstream provider supports baby jumbo frames over PPPoE (where your MTU would be set to 1508 - to give 1500 bytes of packet and 8 bytes of PPPoE header) this could easily work. Andrews&amp;amp;Arnold ISP did some work on this on the BTOR network a few years ago &lt;A href="http://aa.net.uk/kb-broadband-mtu.html"&gt;http://aa.net.uk/kb-broadband-mtu.html&lt;/A&gt;. Not sure if PN support that approach though as im not on the trial. &lt;BR /&gt;Also bear in mind that MTU is not MRU (though they should still be governed by the same ppp link packet requirements). Perhaps the receive path is allowing baby jumbo but not the xmit path? im clutching at straws here, mind you - but logically that would fit. PN would really need to specify what customers need to set as MTU on IPv6 based on the underlying last mile network and any upstream IPv6 carriage paths.&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote from: AndyH&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote from: plexy&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;I can try to validate this if you PM me the IPs you are making requests from&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;PM sent!&lt;BR /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;Grand, I can confirm the Akamai systems know that IP you sent me is Plusnet. I dont see anything untoward that would cause a mapping problem in DNS with your specific IP.&lt;BR /&gt;</description>
    <pubDate>Thu, 08 Jan 2015 18:26:30 GMT</pubDate>
    <dc:creator>plexy</dc:creator>
    <dc:date>2015-01-08T18:26:30Z</dc:date>
    <item>
      <title>Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094511#M2231</link>
      <description>I am getting a lot of Facebook images that aren't loading at the moment and they are delivered/hosted by Akamai (address fbcdn-profile-a.akamaihd.net).&lt;BR /&gt;A traceroute shows exactly the same issue as with &lt;A href="https://community.plus.net/www.java.com" target="_blank"&gt;www.java.com&lt;/A&gt; (traceroute seems to go no further than PN's network):&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;traceroute6: Warning: a2047.dspl.akamai.net has multiple addresses; using 2a02:26f0:5a::173e:3531&lt;BR /&gt;traceroute6 to a2047.dspl.akamai.net (2a02:26f0:5a::173e:3531) from 2a02:16c8:2000:1100:ed61:xxxx:xxxx:xxxx, 64 hops max, 12 byte packets&lt;BR /&gt; 1 &amp;nbsp;2a02:16c8:2000:1100:xxxx:xxxx:xxxx:xxxx &amp;nbsp;0.376 ms &amp;nbsp;0.410 ms &amp;nbsp;0.330 ms&lt;BR /&gt; 2 &amp;nbsp;2a02:16c8:0:1::16 &amp;nbsp;6.601 ms &amp;nbsp;6.363 ms &amp;nbsp;5.997 ms&lt;BR /&gt; 3 &amp;nbsp;2a02:16c8:1:2::19 &amp;nbsp;4.591 ms &amp;nbsp;4.706 ms &amp;nbsp;4.409 ms&lt;BR /&gt; 4 &amp;nbsp;2a02:16c8::d &amp;nbsp;4.647 ms &amp;nbsp;4.575 ms &amp;nbsp;6.129 ms&lt;BR /&gt; 5 &amp;nbsp;2a02:16c8:1:2::8 &amp;nbsp;4.629 ms &amp;nbsp;4.576 ms &amp;nbsp;4.989 ms&lt;BR /&gt; 6 &amp;nbsp;* * *&lt;BR /&gt; 7 &amp;nbsp;* * *&lt;BR /&gt; 6 &amp;nbsp;* * *&lt;BR /&gt; 7 &amp;nbsp;* * *&lt;BR /&gt; 8 &amp;nbsp;* * *&lt;BR /&gt; 9 &amp;nbsp;* * *&lt;BR /&gt;10 &amp;nbsp;* * *&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;A traceroute from Hurricane's LG works perfectly fine:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;core1.lon1.he.net&amp;gt; traceroute ipv6 2a02:26f0:5a::173e:356a numeric&lt;BR /&gt;Target	2a02:26f0:5a::173e:356a&lt;BR /&gt;Hop	Packet 1	Packet 2	Packet 3	Hostname&lt;BR /&gt;1	10 ms	11 ms	&amp;lt;1 ms	10ge3-1.core1.lon2.he.net (2001:470:0:2cd::1)&lt;BR /&gt;2	9 ms	&amp;lt;1 ms	&amp;lt;1 ms	ge-2-1-0-zpr1.lnt.cw.net (2001:7f8:4::4f9:1)&lt;BR /&gt;3	&amp;lt;1 ms	&amp;lt;1 ms	&amp;lt;1 ms	so-0-1-0-r1-IPv6.de.cw.net (2001:5000:0:1::1)&lt;BR /&gt;4	11 ms	2 ms	1 ms	akamai-gw2.lns.cw.net (2001:5000:1100:9::2)&lt;BR /&gt;5	&amp;lt;1 ms	&amp;lt;1 ms	&amp;lt;1 ms	2a02:26f0:5a::173e:3531&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;core1.lon2.he.net&amp;gt; traceroute ipv6 2a02:26f0:5a::173e:356a numeric&lt;BR /&gt;Target	2a02:26f0:5a::173e:356a&lt;BR /&gt;Hop	Packet 1	Packet 2	Packet 3	Hostname&lt;BR /&gt;1	13 ms	&amp;lt;1 ms	&amp;lt;1 ms	ge-2-1-0-zpr1.lnt.cw.net (2001:7f8:4::4f9:1)&lt;BR /&gt;2	1 ms	1 ms	1 ms	so-0-1-0-r1-IPv6.de.cw.net (2001:5000:0:1::1)&lt;BR /&gt;3	1 ms	1 ms	1 ms	akamai-gw2.lns.cw.net (2001:5000:1100:9::2)&lt;BR /&gt;4	&amp;lt;1 ms	&amp;lt;1 ms	&amp;lt;1 ms	2a02:26f0:5a::173e:3531&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;The strange thing is that if I ping6 akamai-gw2.lns.cw.net (2001:5000:1100:9::2) and then immediately afterwards do a traceroute to a2047.dspl.akamai.net (2a02:26f0:5a::173e:3531), it works fine:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;$ traceroute6 fbcdn-profile-a.akamaihd.net&lt;BR /&gt;traceroute6: Warning: a2047.dspl.akamai.net has multiple addresses; using 2a02:26f0:5a::173e:3531&lt;BR /&gt;traceroute6 to a2047.dspl.akamai.net (2a02:26f0:5a::173e:3531) from 2a02:16c8:2000:1100:xxxx:xxxx:xxxx:xxxx, 64 hops max, 12 byte packets&lt;BR /&gt; 1 &amp;nbsp;2a02:16c8:2000:1100:xxxx:xxxx:xxxx:xxxx &amp;nbsp;0.443 ms &amp;nbsp;0.393 ms &amp;nbsp;0.336 ms&lt;BR /&gt; 2 &amp;nbsp;2a02:16c8:0:1::16 &amp;nbsp;128.809 ms &amp;nbsp;88.936 ms &amp;nbsp;57.786 ms&lt;BR /&gt; 3 &amp;nbsp;2a02:16c8:1:2::19 &amp;nbsp;4.883 ms &amp;nbsp;4.462 ms &amp;nbsp;4.632 ms&lt;BR /&gt; 4 &amp;nbsp;2a02:16c8::d &amp;nbsp;5.034 ms &amp;nbsp;4.693 ms &amp;nbsp;4.671 ms&lt;BR /&gt; 5 &amp;nbsp;2a02:16c8:1:2::8 &amp;nbsp;4.291 ms &amp;nbsp;4.044 ms &amp;nbsp;4.420 ms&lt;BR /&gt; 6 &amp;nbsp;lonap.he.net &amp;nbsp;4.609 ms &amp;nbsp;11.987 ms &amp;nbsp;4.885 ms&lt;BR /&gt; 7 &amp;nbsp;10ge3-1.core1.lon2.he.net &amp;nbsp;15.629 ms &amp;nbsp;4.191 ms &amp;nbsp;4.699 ms&lt;BR /&gt; 8 &amp;nbsp;ge-2-1-0-zpr1.lnt.cw.net &amp;nbsp;4.680 ms &amp;nbsp;4.639 ms &amp;nbsp;4.636 ms&lt;BR /&gt; 9 &amp;nbsp;so-0-1-0-r1-ipv6.de.cw.net &amp;nbsp;5.188 ms &amp;nbsp;9.314 ms &amp;nbsp;7.206 ms&lt;BR /&gt;10 &amp;nbsp;akamai-gw2.lns.cw.net &amp;nbsp;5.511 ms &amp;nbsp;5.589 ms &amp;nbsp;5.252 ms&lt;BR /&gt;11 &amp;nbsp;2a02:26f0:5a::173e:3531 &amp;nbsp;4.961 ms &amp;nbsp;5.037 ms &amp;nbsp;4.885 ms&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;Any thoughts?</description>
      <pubDate>Tue, 29 Apr 2014 12:33:39 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094511#M2231</guid>
      <dc:creator>AndyH</dc:creator>
      <dc:date>2014-04-29T12:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094512#M2232</link>
      <description>Might be something wrong on our side here. We've flagged it over to Paul to have a look.</description>
      <pubDate>Tue, 29 Apr 2014 13:11:17 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094512#M2232</guid>
      <dc:creator>Kelly</dc:creator>
      <dc:date>2014-04-29T13:11:17Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094513#M2233</link>
      <description>Perfect. Thanks.</description>
      <pubDate>Tue, 29 Apr 2014 13:21:58 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094513#M2233</guid>
      <dc:creator>AndyH</dc:creator>
      <dc:date>2014-04-29T13:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094514#M2234</link>
      <description>yeah I had akamai slow loading/timeouts on another site also.</description>
      <pubDate>Tue, 29 Apr 2014 13:44:56 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094514#M2234</guid>
      <dc:creator>chrcoluk</dc:creator>
      <dc:date>2014-04-29T13:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094515#M2235</link>
      <description>I've made some changes to stop traffic going over the Akamai PNI links.&amp;nbsp; Hopefully this will be a bit more stable while they have a look at what's going on.</description>
      <pubDate>Tue, 29 Apr 2014 16:13:06 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094515#M2235</guid>
      <dc:creator>paulmh5</dc:creator>
      <dc:date>2014-04-29T16:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094516#M2236</link>
      <description>Working for me fine now - thanks.</description>
      <pubDate>Tue, 29 Apr 2014 16:38:56 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094516#M2236</guid>
      <dc:creator>AndyH</dc:creator>
      <dc:date>2014-04-29T16:38:56Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094517#M2237</link>
      <description>@paulmh5&lt;BR /&gt;Thanks for fixing &lt;A href="http://community.plus.net/forum/index.php/topic,126295.0.html" target="_blank"&gt;http://community.plus.net/forum/index.php/topic,126295.0.html&lt;/A&gt; as well.</description>
      <pubDate>Tue, 29 Apr 2014 16:41:53 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094517#M2237</guid>
      <dc:creator>jelv</dc:creator>
      <dc:date>2014-04-29T16:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094518#M2238</link>
      <description>Fingers crossed Akamai have sorted the issue on their side now so I've enabled the PNIs again.&amp;nbsp; Let me know if you see issues with it.</description>
      <pubDate>Fri, 06 Jun 2014 15:21:21 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094518#M2238</guid>
      <dc:creator>paulmh5</dc:creator>
      <dc:date>2014-06-06T15:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094519#M2239</link>
      <description>Paul,&lt;BR /&gt;&lt;A href="https://community.plus.net/www.java.com" target="_blank"&gt;www.java.com&lt;/A&gt; gives "The server at &lt;A href="https://community.plus.net/www.java.com" target="_blank"&gt;www.java.com&lt;/A&gt; is taking too long to respond." over IPv6!</description>
      <pubDate>Mon, 09 Jun 2014 08:18:38 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094519#M2239</guid>
      <dc:creator>jelv</dc:creator>
      <dc:date>2014-06-09T08:18:38Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094520#M2240</link>
      <description>Odd, its working ok for me this morning.&amp;nbsp; Everything else working for you over v6(Facebook etc..)?</description>
      <pubDate>Tue, 10 Jun 2014 06:06:56 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094520#M2240</guid>
      <dc:creator>paulmh5</dc:creator>
      <dc:date>2014-06-10T06:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094521#M2241</link>
      <description>I can access IPv6 only sites such as &lt;A href="http://loopsofzen.co.uk/" target="_blank"&gt;http://loopsofzen.co.uk/&lt;/A&gt;. &lt;BR /&gt;Firefox is accessing some sites (e.g. &lt;A href="http://www.internetsociety.org/blog/tech-matters/2014/02/google-ipv6-traffic-passes-3-deployment-rate-accelerates-0)" target="_blank"&gt;http://www.internetsociety.org/blog/tech-matters/2014/02/google-ipv6-traffic-passes-3-deployment-rate-accelerates-0)&lt;/A&gt; via IPv6 (I'm using the 4or6 add-on) - although it's doing it's usual of fast&amp;nbsp;fall back to IPv4 on others.&lt;BR /&gt;Tracert:&lt;BR /&gt;&lt;PRE&gt;C:\Users\John&amp;gt;tracert -6 &lt;A href="https://community.plus.net/www.java.com" target="_blank"&gt;www.java.com&lt;/A&gt;&lt;BR /&gt;Tracing route to &lt;A href="https://community.plus.net/www.java.com" target="_blank"&gt;www.java.com&lt;/A&gt; [2a02:26f0:26:3:8e00::1ba3]&lt;BR /&gt;over a maximum of 30 hops:&lt;BR /&gt; &amp;nbsp;1 &amp;nbsp; &amp;nbsp;&amp;lt;1 ms &amp;nbsp; &amp;nbsp; 1 ms &amp;nbsp; &amp;nbsp; 1 ms &amp;nbsp;dsldevice.lan [2a02:16c8:&lt;I&gt;&amp;lt;removed&amp;gt;&lt;/I&gt;]&lt;BR /&gt; &amp;nbsp;2 &amp;nbsp; &amp;nbsp;21 ms &amp;nbsp; &amp;nbsp;21 ms &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp;2a02:16c8:0:1::17&lt;BR /&gt; &amp;nbsp;3 &amp;nbsp; &amp;nbsp;21 ms &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp;2a02:16c8:1:2::17&lt;BR /&gt; &amp;nbsp;4 &amp;nbsp; &amp;nbsp;22 ms &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp;2a02:16c8::c&lt;BR /&gt; &amp;nbsp;5 &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp; &amp;nbsp;20 ms &amp;nbsp;2a02:16c8:1:2::6&lt;BR /&gt; &amp;nbsp;6 &amp;nbsp; &amp;nbsp;23 ms &amp;nbsp; &amp;nbsp;24 ms &amp;nbsp; &amp;nbsp;24 ms &amp;nbsp;40ge1-3.core1.lon2.he.net [2001:7f8:4::1b1b:1]&lt;BR /&gt; &amp;nbsp;7 &amp;nbsp; &amp;nbsp; * &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;* &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;* &amp;nbsp; &amp;nbsp; Request timed out.&lt;BR /&gt; ...&lt;BR /&gt; 19 &amp;nbsp; &amp;nbsp; * &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;* &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;* &amp;nbsp; &amp;nbsp; Request timed out.&lt;BR /&gt; 20 &amp;nbsp; &amp;nbsp; * &amp;nbsp; &amp;nbsp; Destination host unreachable.&lt;BR /&gt;Trace complete.&lt;/PRE&gt;&lt;BR /&gt;&lt;A href="http://ipv6.google.com/" target="_blank"&gt;http://ipv6.google.com/&lt;/A&gt; works.&lt;BR /&gt;I'm seeing the issue on both pcl and ptw gateways.</description>
      <pubDate>Tue, 10 Jun 2014 07:23:33 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094521#M2241</guid>
      <dc:creator>jelv</dc:creator>
      <dc:date>2014-06-10T07:23:33Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094522#M2242</link>
      <description>I can't access &lt;A href="http://ipv6.google.com/" target="_blank"&gt;http://ipv6.google.com/&lt;/A&gt; at the moment.</description>
      <pubDate>Wed, 11 Jun 2014 19:36:46 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094522#M2242</guid>
      <dc:creator>jelv</dc:creator>
      <dc:date>2014-06-11T19:36:46Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094523#M2243</link>
      <description>Both are still working fine for me.&lt;BR /&gt;Have you moved to one of the new BNGs?&amp;nbsp; These will give you a pool address rather than a static if you have that in any fixed config that may cause you a problem.&amp;nbsp; Failing that I'd suggest checking your MTU size as a few people have had issues with that and some v6 services.</description>
      <pubDate>Wed, 11 Jun 2014 21:17:59 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094523#M2243</guid>
      <dc:creator>paulmh5</dc:creator>
      <dc:date>2014-06-11T21:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094524#M2244</link>
      <description>I'm not on a bng (does IPSEC go to bng's?).&lt;BR /&gt;I've not touched anything to do with MTU - so why would Google suddenly stop working? (I can tracert to it)</description>
      <pubDate>Wed, 11 Jun 2014 22:05:58 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094524#M2244</guid>
      <dc:creator>jelv</dc:creator>
      <dc:date>2014-06-11T22:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094525#M2245</link>
      <description>Anyone else having problems with Facebook images again?&lt;BR /&gt;java.com is OK, Facebook just seems a bit iffy from my desktop &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@3681646702FDFD32BCA97E2E5F1BDDD5/images/emoticons/huh.gif" alt="Huh" title="Huh" /&gt;&lt;BR /&gt;&lt;IMG src="http://community.plus.net/wp-content/uploads/2014/06/facebook.jpg" /&gt;</description>
      <pubDate>Thu, 19 Jun 2014 16:39:00 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094525#M2245</guid>
      <dc:creator>bobpullen</dc:creator>
      <dc:date>2014-06-19T16:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094526#M2246</link>
      <description>All OK for me.</description>
      <pubDate>Thu, 19 Jun 2014 17:00:06 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094526#M2246</guid>
      <dc:creator>brueton</dc:creator>
      <dc:date>2014-06-19T17:00:06Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094527#M2247</link>
      <description>Just wondering if anyone is having issues with Akamai over v6 again? I am having issues with Facebook/Instagram images timing out again.&lt;BR /&gt;&lt;IMG src="http://i.imgur.com/zwtYbRw.png" /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 29 Dec 2014 08:40:56 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094527#M2247</guid>
      <dc:creator>AndyH</dc:creator>
      <dc:date>2014-12-29T08:40:56Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094528#M2248</link>
      <description>can you post some direct url's here so can test?</description>
      <pubDate>Mon, 29 Dec 2014 12:07:45 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094528#M2248</guid>
      <dc:creator>chrcoluk</dc:creator>
      <dc:date>2014-12-29T12:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094529#M2249</link>
      <description>Try &lt;A href="http://photos-g.ak.instagram.com/hphotos-ak-xaf1/t51.2885-15/10899153_873421292713054_1539817145_n.jpg" target="_blank"&gt;http://photos-g.ak.instagram.com/hphotos-ak-xaf1/t51.2885-15/10899153_873421292713054_1539817145_n.jpg&lt;/A&gt;&lt;BR /&gt;The images are loading (eventually), but they are taking forever:&lt;BR /&gt;&lt;IMG src="http://i.imgur.com/olC409f.png" /&gt;&lt;BR /&gt;&lt;IMG src="http://i.imgur.com/O3IFst4.png" /&gt;&lt;BR /&gt;&lt;IMG src="http://i.imgur.com/KE304D4.png" /&gt;&lt;BR /&gt;I'm on pcl-bng02 - if I disable v6, then I have no issues with any CDN hosted images.</description>
      <pubDate>Mon, 29 Dec 2014 12:29:24 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094529#M2249</guid>
      <dc:creator>AndyH</dc:creator>
      <dc:date>2014-12-29T12:29:24Z</dc:date>
    </item>
    <item>
      <title>Re: Akamai v6 - peering issue?</title>
      <link>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094530#M2250</link>
      <description>I put&lt;BR /&gt;&lt;PRE&gt;photos-g.ak.instagram.com &amp;nbsp; &amp;nbsp; &amp;nbsp; 2a02:26f0:c8::17c0:a2e1&lt;/PRE&gt;&lt;BR /&gt;in my hosts file as then able to access the image in Firefox via v6. I'm on ptw-ag03</description>
      <pubDate>Mon, 29 Dec 2014 13:00:00 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/Akamai-v6-peering-issue/m-p/1094530#M2250</guid>
      <dc:creator>jelv</dc:creator>
      <dc:date>2014-12-29T13:00:00Z</dc:date>
    </item>
  </channel>
</rss>

