Bitbucket needs to be IPv6-enabled so that systems which have only IPv6 connectivity can actually pull/push updates.
We published AAAA records for all public Bitbucket hostnames at about 18:00 UTC today (19 July 2016), and there's already quite a bit of traffic on the IPv6 addresses even though it's only been about two and a half hours. I'm going to resolve this issue, and ask our UX team to update our docs to include the new addresses.
Since the records were published, we have not seen any corresponding changes in frequency of errors, support tickets, or tweets. If IPv6 has broken something for you, though, then please open a support ticket with details.
Thanks for the suggestion! IPv6 support isn't in our current roadmap, but I've added an issue for it to our backlog. We'll update this issue when we have more information.
I went to a cafe yesterday where curiously the router would only give out IPv6 addresses. Fair enough! Unfortunately, my Bitbucket experience came to a standstill then.
Has there been any effort to move forward on this? This is neither a complicated issue nor does it have a complex or expensive solution. Your upstream network service provider is NTT and they can definitely provide IPv6 connectivity.
Hi everyone - although I don't have a timeline to share, this is definitely something we plan to add. Stay tuned, we're working on it.