Live data from Hacker News

Google Hits 50% IPv6

blog.apnic.net

351–360 of 496 posts

Re: Google Hits 50% IPv6

#351

Literally all we had to do was add a byte to IPv4 and we'd be done but noooo we need to overengineer the next protocol and make it as painful as possible to adopt.

That would be just as hard to switch to and even more complex. If you think ipv6 is over engineered you haven't had to deal with ipv4. (Source routing is a pain)

Re: Google Hits 50% IPv6

#352

Earlier quoted context omitted.

You joke, but its exactly how society thinks about housing…

It is difficult to retire with house equity. Housing is just one element of what you need to have in retirement and after a certain point, and especially in retirement, once the house is what you plan to stay in forever it is better if it is worth less (all other social factors aside) so that you don't pay as much in taxes on it.

The point is usually to sell a big house in a desirable location, buy a modest house in a less posh an tax-lighter location, and invest the difference to have a steady stream of income.

Re: Google Hits 50% IPv6

#353
https://www.google.com/intl/en/ipv6/statistics.html

I've never seen this chart before, was taking a peek from the link in the article. Does anyone with networking knowledge know why IPv6 usage peaks on Saturdays and dips during the middle of the week? (something related to mobile ISPs?)

Re: Google Hits 50% IPv6

#354

Earlier quoted context omitted.

Grandma’s ISP can send RFC 1918 traffic to her router and likely be able to directly connect to every internal host. You should have learned in your CCNA training that NAT makes it harder to send inbound traffic to a system, but doesn’t by itself provide the filtering that a firewall does.

Right, I get that. I can see the ISP angle. But my question was specifically for outside attacks. Tangible, real-world threats in existing ISPs, reachable from the outside.

NAT was not designed as a security boundary. Sure, it may block some kinds of incoming traffic accidentally and as a side-effect disrupt some attacks.

But why would you rather have an always-broken network that might block attackers instead of a deliberate "deny incoming" rule that does exactly what you want -- and that you can punch holes in if desired?

Instead we have apps circumventing this accidental barrier with STUN, uPNP, etc with little/no oversight and we also regularly encounter brokenness.

Re: Google Hits 50% IPv6

#355
post #342

Earlier quoted context omitted.

The way to pressure ISPs to support IPv6 is stupid but effective: 1. Sites that help shoppers choose can add a big visual red flag to any ISP that doesn’t support IPv6. Consumers don’t know what IPv6 is by and large but they do understand seeing a big red flag. 2. Same thing for websites. Add a banner that says “hey your ISP doesn’t support proper internet connectivity which this site utilizes. Contact them to let th…

From a US perspective, for your #1, the idea of people “shopping” for broadband, is astonishing. Most people here have available to them one single DOCSIS provider and that’s it. A few lucky ones have a FTTP option too, but that definitely not available to more than 25% of addresses. (It’s true that you can use cellular for your home internet, but I consider that extremely compromised.)

[deleted]

Re: Google Hits 50% IPv6

#356
post #10

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)

Re: Google Hits 50% IPv6

#357

Earlier quoted context omitted.

You joke, but its exactly how society thinks about housing…

It is difficult to retire with house equity. Housing is just one element of what you need to have in retirement and after a certain point, and especially in retirement, once the house is what you plan to stay in forever it is better if it is worth less (all other social factors aside) so that you don't pay as much in taxes on it.

You usually only need one house to have in retirement, just like you likely won't need a whole /22 in retirement.

Re: Google Hits 50% IPv6

#358
post #342

Earlier quoted context omitted.

The way to pressure ISPs to support IPv6 is stupid but effective: 1. Sites that help shoppers choose can add a big visual red flag to any ISP that doesn’t support IPv6. Consumers don’t know what IPv6 is by and large but they do understand seeing a big red flag. 2. Same thing for websites. Add a banner that says “hey your ISP doesn’t support proper internet connectivity which this site utilizes. Contact them to let th…

From a US perspective, for your #1, the idea of people “shopping” for broadband, is astonishing. Most people here have available to them one single DOCSIS provider and that’s it. A few lucky ones have a FTTP option too, but that definitely not available to more than 25% of addresses. (It’s true that you can use cellular for your home internet, but I consider that extremely compromised.)

Starlink shattered this monopoly in my area.

Re: Google Hits 50% IPv6

#359
post #130

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…

The way to pressure ISPs to support IPv6 is stupid but effective: 1. Sites that help shoppers choose can add a big visual red flag to any ISP that doesn’t support IPv6. Consumers don’t know what IPv6 is by and large but they do understand seeing a big red flag. 2. Same thing for websites. Add a banner that says “hey your ISP doesn’t support proper internet connectivity which this site utilizes. Contact them to let th…

This will work on nerds (aka the HN crowd) but the average person will read that and wonder why they should care when the page loaded. Also, if you keep displaying the banner people will grow accustomed to it and ultimately ignore it.

Re: Google Hits 50% IPv6

#360

Earlier quoted context omitted.

> I wouldn’t want a public ip for all the devices and computers on my home network either. Seems like a huge security risk. The real security risk is thinking that just because you have an internal RFC 1918 address space your security has improved. It's been a decade+ since a firewall being considered a castle/moat of security being best practice. Any IT person that thinks that if they see a device with an 10/8 (or 1…

Home networks are usually, nearly always, not run by anyone who is capable of “paying attention to the rest of their security controls”

Home networks have the same security whether IPv4 or IPv6: CPEs with a default deny rule, and hopefully folks install patches regularly.
Post reply on HN