Top
Best
New

Posted by Aaronmacaron 1 day ago

IPv6 traffic crosses the 50% mark(www.google.com)
773 points | 567 commentspage 6
pheggs 20 hours ago|
while it looks like its slowing down, I am pretty sure it will speed up once IPv4 get even more expensive, sites start to be hosted on IPv6 only and become inaccessible to some users that dont have IPv4. Thats surely going to put pressure on ISPs
usui 20 hours ago||
Outside of hobbyist niche uses, sites won't start being hosted IPv6-only. The financialization of IPv4 addresses will simply get worse and be even more pay-to-play than it is now. Amazon raises the price of IPv4 and everyone goes along as a cost of doing business.
zokier 20 hours ago|||
My prediction is that sites will be half-IPv6 only; backends will be IPv6 and IPv4 traffic will get proxied to IPv6 by CDNs / edge LBs. I think CloudFront for example supports that scenario, avoiding IPv4 costs (in theory).
neojima 11 hours ago||||
Yeah, hobbyist niche sites like these:

https://clintonwhitehouse1.archives.gov/

https://clintonwhitehouse2.archives.gov/

elsjaako 19 hours ago||||
If you have a big site and want as broad an access as possible I agree.

But I wouldn't be surpised if we start seeing self-hosted minecraft or factorio servers with ipv6 only.

pheggs 19 hours ago|||
that may be true, but not being able to access hobbyist sites still feels like "being locked out" of something. My ISP provides /48 IPv6 addresses for free, and I already run a couple sites only on IPv6 - because an IPv4 would cost 20 bucks a month - it's not important enough to me personally to pay that.
snvzz 20 hours ago||
Maybe "think of the children."

There might be a child behind the NAT, thus IPv6 requirement.

jeroenhd 18 hours ago||
With IPv6 privacy extensions it's impossible to tell which device you're talking to inside of a /64. You'd need to do something silly like DHCPv6 to get that kind of remote device-level tracking.
miyuru 21 hours ago||
crossed 50% on Mar 28, 2026, 3 weekends back.

google published the latest data only yesterday, hence the delay.

randompartytime 21 hours ago|
we did it, boys!

despite the smoothbrain naysayers:

https://circleid.com/posts/20190529_digging_into_ipv6_traffi...

finally, the end of the dark tunnel of NAT is in sight, and the internet will be free once more

harg 18 hours ago||
Interesting to see Spain having such low IPv6 adoption. Perhaps that's exacerbated the issues caused there by blocking IPs during football matches that we've seen mentioned in recent HN posts.
zokier 16 hours ago|
Spain has one of the highest FTTx rollouts in Europe though. My theory is that they just prioritized building fiber and there was no money left for ipv6 transition.
Galanwe 18 hours ago||
Every year I just wish someone will come up with IPv4-with-more-bytes and we can switch to it before IPv6 gets another percent usage share.
AndrewDucker 18 hours ago||
IPv4-with-more-bytes is not backwards compatible with IPv4. So you'd have to replace/upgrade every existing network stack, both hardware and software. To get, basically, the same effect as moving to IPv6.
Galanwe 17 hours ago|||
> IPv4-with-more-bytes is not backwards compatible with IPv4

Neither is IPv6

> To get, basically, the same effect as moving to IPv6

The only thing that IPv6 solves which is of interest to 99.99% of the users is having more adressable space. The rest of IPv6 features are either things that nobody asked for, or things which are genuinely worst compared to IPv4.

I consider the mere fact of enabling IPv6 an unacceptable security risk, as I would now have to make sure my IPv4 and IPv6 firewall stack are perfectly mirroring each other. That would be trivial with IPv4-with-more-bytes, it's a nightmare with IPv6.

mrsssnake 15 hours ago|||
Do NAT64 and just worry about IPv6 if not wanting dual stack.

All of IPv6 features are just direct effects of having more space and not. Basically IPv6 "features" is just getting rid of IPv4 workarounds.

vel0city 11 hours ago|||
> I would now have to make sure my IPv4 and IPv6 firewall stack are perfectly mirroring each other.

You'd still have that in your IPv4-with-more-bytes, as you'll still probably end up running dual-stack to address those old-v4-only sites. Or you'd do the same with v6 and run a tunnel to translate those v4-only addresses to your v4-with-more-bytes. So you're in the same situation either way.

mprovost 16 hours ago||||
There were backwards-compatible protocols proposed, such as EIP, but the committee chose a backwards-incompatible protocol for v6. Their assumption was that v4 would run out of space in a single-digit number of years and everyone would be forced to migrate. The past 30 years have shown that not to be the case.

https://datatracker.ietf.org/doc/html/rfc1385

Dagger2 11 hours ago||
They went with SIPP, which was one of the backwards-compatible options. It should be kind of obvious from the vast number of backwards compatibility methods available in v6 that v6 is actually backwards compatible... but for some reason a lot of people either refuse to believe this or have double standards around what counts as compatibility.
pocksuppet 5 hours ago|||
That's what IPv6 is. People get so fixated on being annoyed at IPv6 they forget to actually think. Whatever you invent won't be any better than IPv6. Many people have tried.

If you change the address format even the tiniest amount, if you add one single additional bit, your new protocol is already completely incompatible with all existing IPv4 software and equipment.

blueflow 18 hours ago||
IPv6 is IPv4 with 12 more bytes, right?
spockz 15 hours ago||
And in the mean time, Odido on the Netherlands still don’t support ipv6 on their fiber network…
jwilliams 17 hours ago||
I'm surprised it's reporting is listed <5% - I thought it was pretty much ipv6 first?
ryzvonusef 8 hours ago||
Quick, someone tell slashdot!
benbristow 15 hours ago||
And Virgin Media in the UK still doesn't support IPv6
Ekaros 16 hours ago||
There really should have been proper government pressure and fines long ago.

Say if you have 10% of market share or x million monthly users you must support IPv6 in say 5 years. If not you are fined say 2% revenue per year until you do...

bluGill 16 hours ago|
I'd make it required that ipv6 for all customers has a higher service guarentee than anyone ipv4. If you don't support ipv6 you can't guarentee anything. give two years to to implement it.
johnhamlin 14 hours ago|
I was wondering why someone proposed IPv8
More comments...