NO

The Current Situation

As the world slowly switches to IPv6 and some services are forced to operate on IPv6 only, GitHub and all its subservices do not support the new protocol. IPv4 addresses have become rare and expensive, which sometimes leads GitHub to be unreachable for those operating on the new protocol.

Why This Matters

GitHub missing IPv6 support isn't just a technical inconvenience. It's becoming a problem for businesses as well. Many cloud providers charge extra for IPv4 addresses, leading companies, hobbyist users and sometimes laymans to deploy IPv6-only servers. New ISPs in various countries are forced to use IPv6-only connections because the IPv4 address space is simply exhausted at this point. When they do provide IPv4 access, it's often through shared connections (through CGNAT or end user tunnel services like HurricaneElectric), which aren't excatly stable or reliable.

The Core Problem: GitHub's Silence

The most telling aspect of the discussion thread is what's missing... There is no meaningful response from GitHub or Microsoft. The thread started around 2022, gathering hundreds of comments from frustrated developers. Yet there is no official roadmap, timeline, or technical explanation from GitHub's team.

One user mentioned vaguely remembering a pre-Microsoft era GitHub engineer discussing IPv6 implementation challenges in a talk or blog post. That suggests that GitHub may have considered IPv6 support in the past. It just hasn't been prioritized or communicated transparently.

Technical Complexity vs. Business Priority

Implementing IPv6 for a platform as big as GitHub is very complex. This includes load balancing, CDN integration, security risks, and making sure that everything is compatible across the entire stack. But that's no valid excuse. Many other platforms have managed to make the switch, including for example Google, Meta, Netflix and Cloudflare (to be fair, that's their entire business lmao).

So we see that it's not impossible. The best guess that it's just business, or rather prioritzation. A good IPv6 implementation needs engineering resources and coordination across multiple systems, but it's clearly possible. GitHub's competitors like GitLab already provide IPv6 support.

The Growing Impact

As we move further into 2025 and forseeable future, this limitation is increasingly affecting developers. Being unable to clone repositories, use GitHub's API, or access the platform from IPv6-only environments is terrible. Workarounds like maintaining IPv4 gateways just for access to GitHub undermines the benefits of IPv6-only infrastructure.

The fundamental disconnect is that GitHub has invested heavily in advanced features like AI-powered code analysis while leaving this basic networking protocol unsupported. IPv6 is an internet standard since 1998 and widely adopted since 2012's World IPv6 Launch Day.

Check (dns.google) I have hope

[results will appear here (JS required)]