Considering how long it took AWS to add IPv6 to services across the board, I'm not surprised that it's taking so long. On the other hand, it would be nice if they would be transparent about the challenges or the reason for the delay, rather than radio silence or, at best, "we're working on it."
My ISP (Metronet) uses CGNAT and refuses to touch IPv6. In my case, when I complained that port forwarding didn't work, they gave me a static IPv4 for free, but I have to call back once a year or else they start billing me $10/month for it.<p>I don't need a static IP. I'd be completely fine with a dynamic IPv4 or even dynamic IPv6. But they don't offer that. Just static IPv4 or CGNAT IPv4. Oh well, some day...
For about 4 years I have considered IPv6 first and IPv4 second. If IPv6 has an issue, I consider the service down, not just half down or slightly non operational. If I call an ISP for an IPv6 issue, I say "internet is down" even if IPv4 is working.<p>This policy helped move things forward on the networks I worked on. Lately I did setup a business internet with SLA, I specifically told the ISP I would not accept the contract if the SLA did not mention IPv6 as required.<p>But it is still a lot of battle, where it should be the default.<p>Github not fully supporting IPv6 is a real shame and they should really move things forward to support it quickly.<p>Also, systems should not use IP addresses as a mean of security or authentication, it was a bad idea for IPv4, it is even a worst idea for IPv6. To give you an example of bad firewall behavior, I was checking my electric bill from the train, and suddenly my account got blocked, and it took me a lot of time and effort to fix (physical mail...). My IP changed while I was browsing a page and the firewall didn't like it.
This shortcoming becomes immediately apparent when you try to use certain VMs, like from Vultr, which are IPv6-only with no CG-NAT. You can't clone anything or fetch any release binaries at all.
Meanwhile in both India[1] and China[2] (two biggest countries by Internet users count) IPv6 is mandated by the national policy. Everyone else should do that, otherwise the transition would never be finished. ISPs and other network businesses should be forced to do upgrades by the law or policy, otherwise they will never allocate budget and resources for that.<p>[1] <a href="https://www.indiatimes.com/technology/news/india-sets-new-deadline-for-upgrading-internet-protocol-to-ipv6-heres-why-it-matters-553484.html" rel="nofollow">https://www.indiatimes.com/technology/news/india-sets-new-de...</a><p>[2] <a href="http://www.stdaily.com/English/ChinaNews/202208/e154b19bb5b04093b9f88424bf46ac75.shtml" rel="nofollow">http://www.stdaily.com/English/ChinaNews/202208/e154b19bb5b0...</a>
I think what a lot of people like to miss is that a lot of detection and antispam stuff is not working well on ipv6. A server without any ipv4 is still limited in many more ways than not being able to reach github which probably means there is not a lot of pressure for github yet.
Lots of organizations do not support IPv6. For another example, Heroku does not (and many systems are based on Heroku):
<a href="https://help.heroku.com/I8L6RW01/does-heroku-support-ipv6" rel="nofollow">https://help.heroku.com/I8L6RW01/does-heroku-support-ipv6</a><p>It's unfortunately harder to support IPv6 than I think it should be, so many organizations do not. I'd love to see GitHub support IPv6, but they are by no means the only one.
from the NAT64 gateway in the thread I learned from ipv4 mapped ipv6 addresses<p><pre><code> 2001:67c:27e4:1064::140.82.121.3 github.com www.github.com
</code></pre>
if your curious too, see <a href="https://www.rfc-editor.org/rfc/rfc6052#section-2.4" rel="nofollow">https://www.rfc-editor.org/rfc/rfc6052#section-2.4</a>
I have a dual stack DSL connection and do not particularly favor IPv4 or IPv6. But I just looked at my PiHole DNS statistics and I see that AAAA requests have taken over A requests by now, 47.2% vs 46.2%. Not much but it's something.<p>I wasn't aware that over half of my internet traffic goes over IPv6 already
Well, if Github nowadays runs on Azure under the hood (which they probably don't) I understand. IPv6 support in Azure is patchy with many of their services.