62 comments

[ 4.9 ms ] story [ 82.4 ms ] thread
(comment deleted)
And 32% is all llm/bots using AWS and other "pay for ipv4 IP" use cases.
I wonder if there will ever come a day when IPv6 will provide a better web experience than IPv4.

At the moment pretty much every website is reachable via IPv4 but a lot not via IPv6. Will there be a day when this turns around?

First thing I do on a fresh Linux install is set ipv6 to deactivated. Fixes all my initial Linux install problems. I don't question it, it just works every time.
How does IPV6 affect ip blocking. As a VPN user I wish it wasn't used as a metric for sites shaking you down.
Thread from two months ago (626 comments): https://news.ycombinator.com/item?id=47777894
Thanks! Macroexpanded:

IPv6 traffic crosses the 50% mark - https://news.ycombinator.com/item?id=47777894 - April 2026 (621 comments)

---

Other recent threads, if anyone would like a thousand more IPv6 comments:

The world in which IPv6 was a good design (2017) - https://news.ycombinator.com/item?id=47821429 - April 2026 (166 comments)

IPv6 is the only way forward - https://news.ycombinator.com/item?id=47680124 - April 2026 (339 comments)

IPv6 Adoption in 2026 - https://news.ycombinator.com/item?id=47083086 - Feb 2026 (21 comments)

IPv6 is not insecure because it lacks a NAT - https://news.ycombinator.com/item?id=46696303 - Jan 2026 (577 comments)

Google hits 50% IPv6, very good for accessing websites.

But my TP-Link router blocks by default inbound IPv6 connections, without any option to configure it, still bad for pure IPv6 bidirectional streaming, gaming or services on home networks.

Most people will never touch their router config, so the defaults are important. Default-deny inbound is better than allow. But it's surprisingly dumb that the router won't even let you configure it to allow, you sure there's no option to disable the firewall?
I’ve yet to live anywhere where the available mainstream ISPs were willing or able to provide IPv6 service. I’d be happy to use it, if I were able.

I also have built cloud infrastructure for multiple SaaS providers with tens of thousands of customers over the past decade. Only one customer I’m aware of has ever even requested IPv6 support. And if customers aren’t asking for it, my employers have never been interested in the full network re-architecture required to truly support it internally.

There are still several basic services you can’t run IPv6-only in AWS, and a handful of AWS service features that don’t support it at all.

As a sysadmin for decades now, I’ve always found IPv6 to be overengineered and in many ways completely ridiculous. But I’d love to be supporting it in everything I do. Only I still can’t, even after 20+ years of being lectured about it; even after complete IPv4 exhaustion has been reached. I don’t think we’re ever going to turn IPv4 off. At best it will be progressively hidden, even from technical users. And folks like me will just have to keep building workarounds to patch the holes where IPv6 still doesn’t work.

Noooo, my /22 IPv4 subnet allocation is my personal 401k, I need this money to retire.
Great example of how fixing things "the correct way" does not seem to work sometimes.

They added those new addresses that can store more information.. but this requires a rewrite of old software to make it work.

If they used the old >bolting on top< method by extending ip4 from 4 octets to 8 (or more) octets, then old software could be extended much easier too / probably addresses could be simply mechanically translated too, so ancient software can work.

Meanwhile T-Mobile/Odido in the Netherlands is still not supporting IPv6 despite promising to have been working on it for years.

Ubiquity gateways also seem to not support it sadly. It would be awesome if they supported something like Hurricane Electric’s tunneling.

I made my homepage (www.makonea.com) support IPv6 too, but the number of people actually using it is much smaller than I expected. Is IPv6 really that widely used? I'm supporting both because I heard it's good to support both, but I'm not sure what the actual benefit is. Sometimes, when behind Cloudflare, I think even if someone connects via IPv6, it ends up coming through as IPv4
Likely caused by better performance provided by IPv4.

Browsers try both stacks (Happy Eyeballs algorithm) so likely the IPv4 is working better for your visitors.

Since must people use IPv4 most of the time, IPv6 performance issues go unnoticed by the users, ISPs, CDNs, etc.

Took them long enough. Now if only Google would follow with their own services.

Sure Gmail has ipv6 enabled and routable ip6 MX. but sending to those addresses is often rejected and forced to retry over ipv4.

Don’t get me started on gh

I want Google gone. This company is causing too many problems.

I am still sometimes using Google Search. First results are now almost always videos on youtube, aka self-promo. These videos are in 99.9% of the search results I use, totally useless and worthless. Even searching on youtube has recently gotten worse. It is also crap now. I know that because I bookmark various videos, and I can not find older videos anymore either. I can eliminate some results I don't care via ublock origin hero-blocking this Google garbage, but I really think we should no longer allow this de-facto monopoly to worsen the global situation any longer. The USA is protecting these gangsters - it is time to have true legislation that gets rid of that mafia bloc that is Google.

Cloudflare sees over 40%, and it hasn't gone up in the last year even with the overall traffic increase. Personally, as the APNIC article also says about their own observations, I guess the overall adoption is somewhere in between.

https://radar.cloudflare.com/adoption-and-usage#ipv4-vs-ipv6

But we have to remember that this reflects the adoption on the client side. With many high profile services still IPv4-only, the fraction of IPv6 flowing on the public Internet might be much lower.

I wonder what incentives are needed to push this forward, because it's not the same incentives as years ago for sure. We've long since exhausted new IPv4 allocations.

In America I've never had a non-mobile ISP offer IPv6. At this point it would be best to recognize the sunk cost and give up on the migration. IPv6 will never reach the 100% needed to turn off IPv4.
2026. Literally no reason to be using this outdated limited addressing.

New regex: IP(any collection of numbers and dots).

Now we have infinite IP address possibilities and no one controls the space.

Done.

Specifically on weekends, which seems to indicate that it's the corporate/business network side of things that is not bothering with implementing it.
Just to add to the 'but the ISPs do not' anecdotes, it has been six months since someone last commented so it is probably time to mention this again on Hacker News:

* https://havevirginmediaenabledipv6yet.co.uk/

A major ISP in the U.K., that said in a public statement on World IPv6 Day in 2011 that

> As well as our core and access networks being capable of supporting IPv6, we're rigorously testing our entire network to ensure that all customers have a smooth and simple transition when the time comes to flick the switch and turn IPv6 on. We're really pleased with how our tests are advancing and are happy to say that by the end of 2012, we'll be able to fully support customers looking to switch to IPv6.

has not managed to actually flick that switch in 15 years.

* https://ispreview.co.uk/story/2011/06/08/uk-isp-fluidata-hai...

We're finally getting there in the US, though. Top ASNs are >75% IPv6 capable.

It's Optimum Communications and Frontier (my provider) that are really holding the numbers down at ~15% each. The latter is improving very slowly, but not a lot of evidence of change in the former.

Here in Brazil most ISPs provide IPv6 by now... But what happens a lot, when field technician are installing your broadband, they just... don't configure IPv6. As if IPv4 (CGNAT!) wasn't enough. With bigger ISPs this is less common.

With mobile carriers this is even worse. For some reason, some default config are IPv4 by default, while literally all of them supports IPv6.

Having interviewed with them for a SRE role I can definitely see how they are awful. The amount of technical debt is hilarious.
If you sign up with + in your e-mail address, it breaks their backend too

Fun fun

When I set up a "pure" (not really) IPv6 server, was surprised that Github does not support it. Without the voluntary operations listed at https://nat64.xyz/ , they'd be unreachable from IPv6.
Github’s lack of v6 is completely unforgivable
> Is IPv6 really that widely used? Mobile carriers use it almost exclusively, which is already a huge chunk of the internet, and newer ISPs are switching to it too.
Almost all mobile carriers use v6, but not exclusively. They also hand out a v4 to every customer. The v6-only part is their internal network.
Whenever I turn on ipv6 on my router (isp supports it, dual stack) randomly I get half the download speeds, YouTube video freezes, and eventually a captcha screen on google. The moment I disable v6 even only at the client side I get to max out my bandwidth. Tested on google drive, sites on azure and aws and netflix’s fast.com which show’s your ip just to confirm I was connecting over v6.
Maybe your ISP is really tunneling v6 over v4?
No the server is getting an ipv6 address and verified on those test sites. This seems bad routing.