Try the following:

$ nslookup github.com
[...]
Non-authoritative answer:
Name:   github.com
Address: 140.82.121.3

See also the completely ignored post in their forums.

85 points

comment from the forum:

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.

permalink
report
reply
43 points

Funny how different situations can be. I can’t get an IPv6 address unless I pay for insanely expensive business tiers.

permalink
report
parent
reply
10 points
*

I had a very small cheap ISP in France (Quantic Telecom) and they didn’t even monitor their network for ipv6 issues. I had to report problems myself every other week. They had less than 90% uptime in 2023, so I ended up getting a refund

permalink
report
parent
reply
9 points

Oof, imagine having to put a single 9 into your SLA. You would be laughed out of the room in a commercial setting.

permalink
report
parent
reply
1 point

The IPv4 exhaustion is far more gnarly in developing countries. Something on the scale of hundreds of people sharing one IPv4 address.

If I want to get a public IPv4 address from my ISP, I have to spend extra. Some ISPs in my country simply don’t give public IPv4 addresses anymore. They have completely exhausted their pool.

permalink
report
parent
reply
5 points

Roasted

permalink
report
parent
reply
2 points

I wonder if they ever contacted github support, and what their answer was - rather than only posting on a public forum github doesn’t feel compelled to answer or make official responses to.

permalink
report
parent
reply
84 points

“IPv6 is not a feature; its absence is a bug”

  • Someone on the Flathub repo, I think
permalink
report
reply
29 points

I always use Github to check if my IPv4 DNS works lol (using ping). So it’s definitely a feature /s

permalink
report
parent
reply
3 points

When you’re relying on a bug as a feature

permalink
report
parent
reply
27 points

I’ve still never used ipv6. It just never offered anything I needed.

permalink
report
reply
47 points

If you live in the USA you don’t suffer from the problem it solves because you have ~5 IP v4 addresses per capita (totaling to 41% of all the IP v4 addresses), and likewise many european countries have ~2 per capita (although there are expeptions like Italy and Spain which are a bit under 1 per capita). However many other countries don’t have such luxury, for example in india there’s one for every 36 people, which is obviously not enough and thus they have to either use NAT everywhere or switch to IPv6.

permalink
report
parent
reply
20 points

I’m in Indonesia right now. Stuff can be randomly offline or blocked because they think I’ve already accessed or am spamming something. Even little things like New York Times saying “you’ve reached your free limit for today” but I didn’t even have internet access for a couple of days!

permalink
report
parent
reply
3 points

There isn’t 5 addresses per person in the US. They use NAT like everyone else. I think you know this though.

permalink
report
parent
reply
8 points

No the number is public. The IPv4 addresses allocated to the US are about 1.524 Billion, and there are ~332 million people in the US. Most of those IPv4 addresses are allocated to servers in datacenters, but individual people having a public IP for their house is really common. Yeah, your devices are behind NAT, but you can get one. To their point, in countries like India, people outnumber IPv4 addresses so much this isn’t possible. Just getting people there online in a way they can interact with the IPv4 Internet is tricky to do well.

permalink
report
parent
reply
-35 points

Have you tried being less poor?

permalink
report
parent
reply
2 points
*
Deleted by creator
permalink
report
parent
reply
1 point

No

permalink
report
parent
reply
-2 points

Luckily for me I’m not poor.

permalink
report
parent
reply
9 points

Same. I’m hearing it’s a must-have for like 15 years now. It still obviously isn’t a real must-have.

permalink
report
parent
reply
18 points
*

This is because ISPs keep piling on workaround after workaround in order to scale their use of IPv4, which is working but not without some disadvantages. Also, like other commenters mentioned, the western world have an unfair advantage in IPv4 addresses allocation and thus people living there don’t really see any meaningful shortage of IPv4. People in other countries don’t have this luxury and have to rely on IPv6 and shitty CGNAT in order to stay online.

permalink
report
parent
reply
-1 points
*
Deleted by creator
permalink
report
parent
reply
15 points

Depends on where you are. It’s a must-have in parts of the world that don’t have enough IPv4 addresses.

permalink
report
parent
reply
8 points

I remember hearing that it meant every device could have a unique IP. But we still have NAT…

permalink
report
parent
reply
2 points

You don’t have NATs in the IPv6 world…

permalink
report
parent
reply
5 points

You may have.

For example, T-Mobile in many places gives you an IPv6 address and uses CG-NAT for IPv4 — meaning you don’t have your own IPv4, but you do have a few quintillion “real” IPv6’s to yourself.

permalink
report
parent
reply
20 points

How hard is it to support IPv6? Does it require new hardware?

permalink
report
reply
19 points

I used to study networking, albeit at a pretty beginner level. IPv6 has been around for nearly 30 years at this point, so I’d be surprised if the hardware github uses doesn’t support it. The impression I got was that it’s pretty easy to extend an IPv4 address space so there isn’t any rush to make a large scale move to IPv6 everywhere.

permalink
report
parent
reply
12 points

It’s not generally a hardware problem. It’s a resourcing problem. Companies like GitHub will have complex software and architecture. IPv6 requires them to get a pool of IP addresses, come up with an IP address management strategy, make sure all hosts have IPv6 addresses meaning that now provisioning systems and tooling to management DNS has to plumb IPv6 addresses through too.

Then the software stack has to support it. Maybe their fraud detection or auditing systems have to now support IPv6 which means changes to API schemas.

None of this is a good reason why they shouldn’t do it, but I’ve had to make similar decisions at my job as a software engineer on what looks to be simple but actually requires changes across systems.

permalink
report
parent
reply
15 points

This is just sad.

permalink
report
reply

Programming

!programming@programming.dev

Create post

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



Community stats

  • 3.2K

    Monthly active users

  • 1.8K

    Posts

  • 30K

    Comments