Facebook Now Available Over IPv6 (Two Weeks Early)

Facebook logoWith two weeks to go until World IPv6 Launch, word started circulating today in social networks that Facebook had enabled IPv6 for their site two weeks early. A quick use of “dig aaaa” shows that yes, indeed, Facebook is now publishing the quad-A record for IPv6:

;; ANSWER SECTION:    9    IN    AAAA    2a03:2880:10:1f02:face:b00c::25


If you have an IPv6 connection and want to test it directly, you can simply go to this URL:


and you’ll be looking at the standard Facebook screen.

Kudos to the Facebook team for making their site live over IPv6 two weeks prior to World IPv6 Launch – and they certainly get bonus points for figuring out how to add their branding into their IPv6 address! 😉

P.S. Have you registered your website to join World IPv6 Launch?

(Hat tip to @zajdee on Twitter where I first saw news of the change.)

UPDATE: A commenter on Hacker News pointed out that right now Facebook’s IPv6 address simply redirects to the IPv4 website, meaning that if you were on an IPv6-only network you couldn’t get to the site. So it would seem my celebration was a bit premature and Facebook is still in the process of getting everything set for World IPv6 Launch. Regardless, it’s great to see the IPv6 support happening!

5 replies on “Facebook Now Available Over IPv6 (Two Weeks Early)”

Yes, I noticed that, too… and perhaps that’s yet another sign that their full IPv6 support is still underway.

The commenter on hacker news is incorrect, they are being redirected because the host doesn’t match. Just the fact that it returns a redirect means its being hosted over ipv6.
This works:
curl -g -H “” -H “User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.46 Safari/536.5” “http://[2a03:2880:10:1f02:face:b00c::25]”

Couldn’t make a request to :443 via the 6-to-4 Gateway my ISP provides for the PPPoE/DHCPv6-unable customers.

Using the nativ IPv6 connection my servers have in the datacenter I was able to request and actually getting a response.

So I think FB doesn’t want to have traffic through (unreliable) 6-to-4 gateways and makes the browser to fallback to IPv4.

Anyhow, just a wild guess…

Comments are closed.