I am unable to understand what in 2022 still holds full IPv6 support for a platform like GitHub.
Even if there is already a work in progress for this it is more useful to disclose a proper ETA rather than a "we are working on it" with no ETA.
Thanks

New ISPs in my country are IPv6-only because there is no new IPv4 space to be provided to them. They do have a over-shared IPv4 address by CGNAT but due to the oversharing, it is unstable and not rare to be offline. For these companies, the internet access is stable only in IPv6.

Thinking about the server-side, some cloud providers are making extra charges for IPv4 addresses (e.g.: Vultr.com) so most of the servers in my company are IPv6-only. Cloning github repositories is very cumbersome due to the lack of IPv6 support and this issue affects me and my team mates on a daily basis.

The math is simple: there are 4.88 billion internet users in the world but the IPv4 space only provides 4 billion addresses. It's over: IPv4 is obsolete and is provided in a legacy mode. Current applications and services must be IPv6 enabled otherwise it should be seen as obsolete. For that matter, Github.com is an obsolete service because it relies on obsolete technology as IPv4.

I really tried to use github in a IPv6 Only Network and I was not successful.
We are not talking about a new feature request or a little detail, we are talking about the current standard protocol of the Internet defined by IANA.

Is there any plan on the github's roadmap to fully adopt IPv6?

If GitHub can't get v6 on GitHub.com soon, maybe at least an ipv6.github.com proxy for SSH git cloning?

IPv6 is the actual internet protocol, while IPv4 is a legacy protocol. Please, priorize this request.

My private ci is forced to go full IPv6 only, and this requires me to have one IPv4 gateway to access github. This in turn means I keep running into rate limits all the time. For now I've worked around this with an access token, but that's not sustainable.

Any ipv6 support would be much appreciated.

Is GitHub deprecated or why there is still no IPv6 support? We are talking about a over 20 year old technology and the standard for about 5 years.

Probably because people that manage the technical team still didn't realize what this mean and didn't prioritize it enough.
Every time I get as an answer that something like "there are many complex things that must be taken into account and it is not easy to adust everything to make it happen. It is in the roadmap"

Well, then why hasn't all that been done beforehand and being carried out gradually that we can some progress on it ? Are there people working dedicated to make that happen ?
The lack of these answers makes it look like that is being treated as something minor or less important.

After companies like Google, Facebook, Netflix, Akamai, Cloudflare have made it 100% I don't see any other strong arguments for companies use complexity as a reason to delay it further.

Hope someone from GitHub's team is reading it.

I vaguely remember that years ago (pre-MS, pre-pandemic) somewhere Github engineers held a talk (or maybe it was a blog posting?) which more less said that IPv6 is in the makes, but less trivial than one might think. I just can't find that talk or slides or so anymore. I also vaguely remember that they mentioned ipv6.github.com — which exists, but is just a (probably wildcard-) dummy page which just points to https://ipv6.github.io/ (likely also a DNS wildcard) which then just states that there is no content yet. Probably because it (nowadays?) belongs to the Github user @IPv6. And the Wayback Machine only has a record from 2022 of that site. Maybe someone else remembers where that talk or blog posting was published.

What I though have found is that there is an ipv6 label in Github's blog — it though only lists one posting so far, which talks about Github Pages now having IPv6 support.

There even once was github-ipv6.com which worked as a reverse proxy according to this Reddit comment, but since it no more exists, I guess they got a DCMA takedown or cease-and-desist noticed for using the Github trademark.

But yeah, another Github user here with (on purpose) trying to run hosts IPv6 only and the first (and so far only) hard stumbling block was not being able to clone Git repos from Github.

I wonder if I should use Gitlab.com for these repos, because they do have an AAAA record for their main site:

→ host -t AAAA gitlab.com
gitlab.com has IPv6 address 2606:4700:90:0:f22e:fbec:5bed:a9b9

It's 2022, World IPv6 Launch Day was 10 years ago. Yet, GitHub still doesn't have IPv6 support. The IPv4 address space is exhausted for years now, and ISPs are using techniques such as CGNAT to still be able to give their customers access to the legacy IPv4 internet, with the instability of these techniques as the cost.

Why doesn't GitHub provide native IPv6 support? And, more importantly, is IPv6 support for GitHub on the roadmap?

CC rust-lang/cargo#10711 this causes real issues for open source software users. This is an absurd conversation in 2022.

This is $MS. This company was and will be ever a enemy of open source or new technologies that comes not from $MS. They did nothing that helps the community. $MS is only interested in earning money and gives a shit on your needs

How can you not have ipv6? Some cloud providers charge extra for ipv4!

Would any Github/Microsoft representative tell us in which year, century or millenium will they support IPV6?

We have public cloud environments where we are with IPV6 only already...

Although, based on recent experience with Azure, I think their public cloud environment is also like with 10 years behind Google and Amazon's public cloud anyway. Why would they bother for Github?

Could we possibly just have a proxy service for Git over HTTPS cloning? Even read-only cloning of public repos would be quite helpful for building on IPv6-only servers.

Since there is still no official response, I've decided to provide a proxy myself. Feel free to clone via my proxy. More details here: https://danwin1210.de/github-ipv6-proxy.php

It is absolutely time for IPv6 support. According to Google https://www.google.com/intl/en/ipv6/statistics.html we are at 40% worldwide deployment right now.

Many here asked why. My personal guess would be they run legacy hardware and software stack, that don't natively support IPv6, and at GitHub internally it may not simply be "turn on the IPv6 switch", but rather replace these 200 routers and perhaps re-develop some pieces of internal software.
We are all developers here, so no need to explain the obvious, that re legacy applications from the 00s built only for IPv4 it may be better to just redevelop the whole thing with a modern software stack.

Who knows what skeletons they have in their closet, but chances are if it was just flipping a switch, they would have done so already. Probably it is as much an organizational and prioritization problem, as it is a tech one.

Whatever skeletons they may still have there are not excuses of complexity or whatever to be so late at this stage.

Several even more complex scenarios to mention as Google, Facebook, Netflix, Akamai, etc all have full IPv6 support on their services.

Via being a paying personal customer and my company also being a paying customer, I've logged this request via our support multiple times. I've even asked at GitHub events. Each time getting very little reason as to why we can't have Git operations (that are mainly SSH and HTTPS) over IPv6.

There was responses it was in the works, and even a brief discussion about my company helping to test it. That just all fell away and I was never given an estimated time for this to happen. Please GitHub lets get a plan of action underway for this. It's bit me time and time again. I'm sick of running dual stacked proxies to just access very few things, GitHub being one.