<story><title>Introducing Pseudo IPv4</title><url>http://blog.cloudflare.com/eliminating-the-last-reasons-to-not-enable-ipv6</url></story><parent_chain></parent_chain><comment><author>X-Istence</author><text>Except that in the past I&amp;#x27;ve had major issues with Cloudflare&amp;#x27;s IPv6 service, recently one of the issues was that Centurylink customers (at least in the Denver area) were unable to visit any Cloudflare hosted IPv6 sites.&lt;p&gt;&lt;a href=&quot;https://twitter.com/bertjwregeer/status/470243728473325568&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;bertjwregeer&amp;#x2F;status&amp;#x2F;470243728473325568&lt;/a&gt;&lt;p&gt;Was my Tweet to Stackoverflow regarding the issue.&lt;p&gt;Here is the paste of the symptoms seen:
&lt;a href=&quot;http://paste.ofcode.org/XQGqerxCNXwYsHDQMZ3aja&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;paste.ofcode.org&amp;#x2F;XQGqerxCNXwYsHDQMZ3aja&lt;/a&gt;&lt;p&gt;This meant that until I reported the issue to Cloudflare&amp;#x2F;StackExchange that people using IPv6 were UNABLE to access those resources needed to load the site (the server would hang indefinitely, so happy eyeballs did not work!). In the case of StackExchange on Centurylink that meant that CSS and other resources did not load, for my site (&lt;a href=&quot;http://defcne.net/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;defcne.net&amp;#x2F;&lt;/a&gt;) that meant my site didn&amp;#x27;t load at all!&lt;p&gt;I absolutely love Cloudflare, but to me it is inexcusable that there is no monitoring to verify that these issues don&amp;#x27;t exist. It took me filing a report for them to fix the issue.&lt;p&gt;Ultimately it came down to this:&lt;p&gt;&amp;quot;We had recently been experiencing IPv6 routing issues with one of our upstream providers for some of our data centers which may have contributed to the issues you had been seeing. We&amp;#x27;ve since disabled transit for that provider to temporarily work around the issue.&amp;quot;&lt;p&gt;Yet this meant that my site&amp;#x2F;StackOverflow and countless other sites using Cloudflare were offline (if the customer has IPv6 enabled) for almost a week (first report from customer using CenturyLink, me trying to figure out what is going on, to CloudFlare fixing the issue).</text></comment>
<story><title>Introducing Pseudo IPv4</title><url>http://blog.cloudflare.com/eliminating-the-last-reasons-to-not-enable-ipv6</url></story><parent_chain></parent_chain><comment><author>mischanix</author><text>&amp;gt;IPv6 can be adopted without a performance penalty&lt;p&gt;Sadly, in my case, this is untrue.  If I enable v6 on my Comcast home connection, I see routes with consistently higher latency--around 50ms more for paths within the U.S. such that even a 200 mile destination (HSV =&amp;gt; ATL) is ~70ms away.</text></comment>