[163460] in North American Network Operators' Group
Re: Facebook broken over v6?
daemon@ATHENA.MIT.EDU (Rikard Johansson)
Sat Jun 8 16:14:53 2013
In-Reply-To: <51B38818.2080400@b2b2c.ca>
From: Rikard Johansson <rj@telia.net>
Date: Sat, 8 Jun 2013 22:13:36 +0200
To: Chris Conn <cconn@b2b2c.ca>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
M=C3=A5ste vara n=C3=A5t med browsern. Fortsatt god helg!=20
Test IPv6
FAQ
Mirrors
Stats
Test your IPv6 connectivity.
Summary
Tests Run
Share Results / Contact
Your IPv4 address on the public Internet appears to be 213.65.35.162
(TELIANET-SWEDEN TeliaSonera AB)
Your IPv6 address on the public Internet appears to be 2001:2002:d541:23a2:1=
1fe:f37f:1493:bb73
(TELIANET TeliaNet Global Network)
It appears that you use a non managed tunnel mechanism for either IPv4 or IP=
v6. [more info]
Good news! Your current configuration will continue to work as web sites ena=
ble IPv6. [more info]
Your browser is blocking the test urls. We will try alternate methods, but t=
hey may fail to show your IP address; and may affect the quality of the advi=
ce given. [more info]
Your browser blocked http://ipv6.test-ipv6.com/ip/?callback=3D?&size=3D1600&=
fill=3Dxxx...xxx
You appear to be able to browse the IPv4 Internet only. You will not be able=
to reach IPv6-only sites.
IPv6 connections work, but connections using DNS names do not use IPv6. For s=
ome reason, your browser or your OS is not doing IPv6 DNS 'AAAA' lookups. [m=
ore info]
Your DNS server (possibly run by your ISP) appears to have IPv6 Internet acc=
ess.
Your readiness score
0/10 for your IPv6 stability and readiness, when publishers are forced t=
o go IPv6 only
Click to see test data
(Updated server side IPv6 readiness stats)
=20
Copyright (C) 2010, 2012 Jason Fesler. All rights reserved. -- r1190
Mirrors | Mission | Source | Email - - Attributions=20
This is a mirror of test-ipv6.com. The views expressed here may or may not r=
eflect the views of the mirror owner.
Sent from my mobile phone
On 8 jun 2013, at 21:38, Chris Conn <cconn@b2b2c.ca> wrote:
> On 2013-06-08 15:29, Chris Conn wrote:
>> It's affecting anyone running dual stack, as the server responds, hangs, t=
imes out and then it tries again on v6. At least in the latest FF and Safari=
browsers, I've not tried chrome. I've cc'd this over to Nanog, as I've not s=
een anything about it there, and I'm sure others are seeing it. www.v6.faceb=
ook.com works fine as a workaround for the time being. --
>=20
> Indeed, I have seen this behaviour for at least a week. It seems to someh=
ow be related to geo-located DNS (akamai?) since the timeouts and RSTs I see=
in the traffic are from IPv6 akamai servers, not facebook itself.
>=20
> I tried de-peering from a number of networks to try and isolate it and it w=
as not transit-specific. I stopped questioning my network when I saw a thre=
ad on Sixxs and tunnelbroker about this very issue.
>=20
> Hopefully it won't persist as right now as having Facebook intermittently c=
onnect is likely hurting deployment slightly.
>=20
> Chris
>=20
>=20
>=20
>=20
