Live data from Hacker News

IPv6 traffic crosses the 50% mark

google.com

171–180 of 643 posts

Re: IPv6 traffic crosses the 50% mark

#172
Can someone reconcile for me the constant chatter about how IPv6 isn't getting impemented, versus this result that more than half of all traffic (as measured by google) is now IPv6?

It sounds to me like its a tool which is available to be used when needed and when no better workarounds exist, and it is slowly but surely being adopted as needed.

Re: IPv6 traffic crosses the 50% mark

#173
post #133

NB: this is not "IPv6 traffic crosses the 50% mark" but "availability of IPv6 connectivity among Google users", which is a very important difference. This means roughly half of Google users have IPv6 capability , which does not 1:1 correspond how much traffic is actually transferred over IPv6, which is what this submission says in the title.

It also means you're excluding China, who has has it as a long-term priority to deploy IPv6 and have made huge strides.

Re: IPv6 traffic crosses the 50% mark

#174

As a French national, I am surprised to discover we are topping the charts according to this analysis. Does anybody know why that might be the case? What's the story of IPv6 deployment in France?

I worked with the internet society to mobitor ipv6 adoption for the top million sites ipv6matrix.org it's broken down by country so might answer some of your curiosity

Re: IPv6 traffic crosses the 50% mark

#175

Earlier quoted context omitted.

Do we know any technical reason for this? Or are we left to think this is somehow a political thing?

Outdated beliefs probably. When I talk about v6 support in our b2b saas, PM laughs and says nobody uses that shit. Big tech are massive laggards on this funnily enough.

Definitely not for the biggest ones. Google and Meta have so many machines in their data centers that IPv6 addressing becomes a technical necessity due to the risk of exhausting the RFC 1918 address space. Naturally, they were early adopters of IPv6.

Re: IPv6 traffic crosses the 50% mark

#176

One of the foremost obstacles to wide adoption is that IPv4 still works great and it's ubiquitous. There is no advantage or up-side to deprecating or abandoning IPv4 support at all. The only result of disabling IPv4 is a denial of service to a certain sector of customers or clients. The only way this will change is by increasing pressure on the resource of IPv4 networks. It was a few years ago that AWS broke the news…

Yeah the reality is that the Internet is centralized now. There is no reason for two computers on the internet to connect to each other anymore, as long as you can reach Google/Microsoft/Amazon/CloudFlare, that's all anyone needs.

Just log onto AOL and type in keyword "WALMART" and save! It's friendly and safe.

Re: IPv6 traffic crosses the 50% mark

#179
I am in the middle of building infrastructure in GCP. The workload is your typical stateless web + db workload.

As of now, there is no way to have a 100% internal ipv6. Many of the services, including CloudSQL or the connection between external and internal load balancers do not support ipv6, even when the external load balancer support ipv6 forwarding rules at the front end.

This means that careful internal ipv4 allocations still matter.

Re: IPv6 traffic crosses the 50% mark

#180
post #147

Earlier quoted context omitted.

Perhaps a little tin foil hatty and definitely not the only reason but Microsoft owns Github and also makes a boatload of money off of Azure. Incumbent cloud providers like Azure have a major advantage in terms of having plenty of IPv4 addressing available whereas a new entrant to that market would have to buy or lease that space at a premium. Thus, these companies have an incentive to keep IPv4 a necessity.

IPv4 is going to be a necessity for many many decades no matter what Microsoft do. Even when IPv6 is at 99%, people aren't going to want 1 in every 100 people to not be able to access their site at all. It'll need to be like 99.9% before we start seeing serious IPv6-only services.

Sure, but the implementation in the public clouds is totally backwards.

What they should have done is have their core network default to IPv6 with IPv4 an optional add-on for things like public IP addresses, CDN endpoints, edge routers, VPNs, etc...

Instead, their core networks are IPv4 only for the most part with IPv6 a distant afterthought.

Post reply on HN