A non-trivial minority of the time, they don't support IPv4 either!

> And still, in the year of our lord 2026, GitHub does not support IPv6.

Especially given that it is now owned by Microsoft, which has been working on IPv6-only (at least on their corporate network) for almost a decade:

* https://blog.apnic.net/2017/01/19/ipv6-only-at-microsoft/

* https://www.arin.net/blog/2019/04/03/microsoft-works-toward-...

Same with Twilio. We have an internal server that does system alerts. We recently moved it to an IPv6 only host, and a few weeks went by and noticed there were no longer receiving alerts.

Turns out we could not connect to Twilio's API which is IPv4 only.

Our university has bad problems with ipv4. Every few days you'll notice some websites being unreachable, including github. Although with their uptime recently, you never know who's to blame...

They supported IPv6 for a short time, but then stopped their experiment.

An excellent reason to move away from Github, I find.

Just found this little site. https://isgithubipv6.web.app/

Maybe we shouldn't even measure percentage adoption and instead just if github has finally adopted..

GitHub should absolutely support IPv6, but until then... transip.eu provide IPv6 addresses which transparently proxy to github.com: https://www.transip.eu/knowledgebase/5277-using-transip-gith...

You'll need to update your DNS server to include those as AAAA records.

Do providers like NextDNS or RethinkDNS allow these sorts of overrides?

Do we know any technical reason for this? Or are we left to think this is somehow a political thing?

The irony of this is that pretty much all they'd have to do to enable IPv6 support is to use Azure Front Door as their CDN. Or... use any other CDN, they pretty much all default to providing IPv6!

Came here to exactly check on this to see if there are any changes on Github side too

Most websites still don't