Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I own 2048 IPv4’s myself and their value is ever increasing. Like digital real estate, without the fluctuation of crypto.

Until the day when ipv6-only connectivity becomes practical/commonplace. At some point ipv4 market is going to crash when they are simply not needed anymore. Of course that inflection point might still be quite far away, but I wouldn't count on ipv4 stock being a retirement fund



> Until the day when ipv6-only connectivity becomes practical/commonplace.

IIRC, this has already occurred for mobile phones.

* https://blogs.akamai.com/2016/06/preparing-for-ipv6-only-mob...

It's (one off?) the reasons why Apple mandates that apps work with IPv6-only networks:

* https://developer.apple.com/support/ipv6/


T-Mobile did it in the US.

And a lot of Indian providers as far as I know.

Most still doing either v4 only with CG-NAT or dual stack.


This is slowly happening. On my blog, I can see IP addresses of people who subscribed for my newsletter. It used to be 100 per cent IPv4 a year ago, now it is more like 8:1.


But you still need an ipv4 address even if it’s only 10% of people who are ipv4 only.


Not exactly. At 70% (like today in much of the world) that's certainly a practical option for most people. At 10% not so much.

So what happens is that beyond a certain point it stops making commercial sense to route IPv4 globally. That's probably before your 10% mark. So by then there's no point bothering with IPv4 for your systems unless you specifically serve that deprived market and will spend money to connect to them specially.

For IPv4 users the Internet still mostly works, when their system asks "A? some.website.example" and there is no A record because the IPv4 Internet isn't really a thing any more, it gets an answer like "10.20.30.40" where that address was arbitrarily picked as a temporary local assignment for some.website.example. When they connect to 10.20.30.40 a Network Address Translation module behind the scenes does an IPv6 connection to some.website.example and hooks them up.

So their copy of Internet Explorer still "works" although some more advanced features are flaky or missing but hey, they know they have crappy 20th century Internet and ought to upgrade.

Inside some larger companies there already is no IPv4, and that will spread, inconsistently but it will spread, because IPv4 is a pain in the backside, it's easier without it. Translation gateways keep things mostly working enough for people who have IPv4 only, today that's the majority, a decade from now it's a minority, and eventually it's too few people to care about.

Eventually (probably much below 10%) the translation gateways are thinly used enough that "nobody" proactively notices if they're broken, that'll happen in some places faster than others, but the effect is to push those final people to upgrade because it's just annoying to always be the person calling your ISP to complain when it breaks.


If 90% of users are on IPv6, you as a content producer are unlikely to need IPv4 at $20/IP (or rather, $5120 per /24).

If 90% of content is on IPv6, you as a user are unlikely to need an IPv4 address.


Fewer and fewer people are able to get an IPv4 address - that's the main reason for IPv6 !


But some people (like myself) are unable to get an ipv6 right now.

Some people are unable to get ipv6 from their cloud hosted servers outbound right now too. Even if they tried.



You still need one IPv4 address per app or maybe per CDN. It's very few addresses.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: