3 ms·
At the rate it's going, IPv6 should be ready for prime time around the same time we have nuclear fusion power plants and real self-driving cars that don't rely
by dlcarrier 2y ago
At the rate it's going, IPv6 should be ready for prime time around the same time we have nuclear fusion power plants and real self-driving cars that don't rely on a human driver.
- redrove 2y ago> nuclear fusion power plants and real self-driving cars that don't rely on a human driver. I think both of these are much closer to reality than IPv6 adoption.
- 9x39 2y agoWell, it did go from single digits in 2014 to 40-something percent adoption in 2024. Who knows where a tipping point is, though, or the emergence of more utility for it. https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- Arnavion 2y agoI was surprised to learn from the submitted article that Discord and Reddit also don't support v6, because those two ought to have a large mobile phone userbase, and mobile networks are the biggest cases of publicly routable v6 addresses and CGNAT for v4.
- ale42 2y agoDepends where, though. Here in Switzerland I think that only one of the three main mobile operators (Swisscom) has IPv6 on their networks (and it's a 2024 thing, so not even sure it's already reaching all customers).
- kiwijamo 2y agoIndeed. Here in New Zealand none of the mobile carriers have deployed IPv6 on mobile (and there are apparently no plans to do so) so we are at 0% for Mobile IPv6. Meanwhile all except one of the major fixed line carriers have IPv6. I don't have % figure but I would estimate >50% of fixed line connections here have IPv6 enabled (at least at the provider's end).
- Sesse__ 2y agoInteresting, I had IPv6 on a “beta” Swisscom in 2016 or so. Crazy that it's taken them to long to productionalize it.
- zamadatix 2y agoReddit is an odd half mix. It seems like most everything they have is dual stack, including the CDN and "reddit.com"... but the "www.reddit.com" page you get redirected to is itself IPv4 only (and maybe some authentication endpoints or something, I haven't looked lately). They'll probably get there shortly. Discord is an interesting one. On GitHub they've more or less straight out said "we built our backend with a bunch of hardcoded ipv4 addresses and logic and it hasn't been a priority to go back and fix vs build out the app".
- jeroenhd 2y agoSomething to consider about those statistics is that they don't include mainland China's massive IPv6 adoption, because the great firewall of China isn't going to "just" let you use Google. The Chinese government is actively pushing ISPs to deploy IPv6 to the point where [it's banning IPv4 NAT devices starting next year](https://www.lightreading.com/regulatory-politics/china-directs-telcos-again-to-speed-up-ipv6-adoption https://www.lightreading.com/regulatory-politics/china-direc...). If you do see traffic from mainland China, it'll probably be through a VPN, and VPNs tend to be IPv4-only. Most companies and servers probably won't care about Chinese visitors, but that still comes down to 763 million internet users that don't show up in the IPv6 statistics for companies like Google.
- lovich 2y agoAWS provides a dual stack option that lets you run ipv4 and ipv6 simultaneously. We used it to help aid in a mostly uneventful migration over to ipv6 for most of our applications
- throw0101a 2y ago> At the rate it's going, IPv6 should be ready […] It's ready now. T-Mobile US is IPv6-only on handsets, as are many other carriers: * https://www.youtube.com/watch?v=nNMNglk_CvE https://www.youtube.com/watch?v=nNMNglk_CvE Microsoft went towards IPv6-only in corporate networks so that their IPv4 address could be moved to Azure to generate revenue: * https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/ https://www.arin.net/blog/2019/04/03/microsoft-works-toward-... See also Google and their offices: * https://www.youtube.com/watch?v=hb98hAb5_W8 https://www.youtube.com/watch?v=hb98hAb5_W8 Facebook/Meta is IPv6-only in their DCs: * https://www.youtube.com/watch?v=IKYw7JlyAQQ https://www.youtube.com/watch?v=IKYw7JlyAQQ According to Google, the US and UK is half IPv6 (France and Germany are >75%): * https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption https://www.google.com/intl/en/ipv6/statistics.html#tab=per-...
- RunningDroid 2y ago> T-Mobile US is IPv6-only on handsets… N=1 but T-Mobile US appears to be IPv6 enabled, not IPv6-only: https://i.imgur.com/ZPi398P.jpeg https://i.imgur.com/ZPi398P.jpeg
- throw0101a 2y ago> N=1 but T-Mobile US appears to be IPv6 enabled, not IPv6-only: https://i.imgur.com/ZPi398P.jpeg https://i.imgur.com/ZPi398P.jpeg "On handsets". If you look at the HTML source of that page you'll see: <p id="ipv4-head" class="public-ipv4-address"> My Public IPv4<!-- --> : <span id="ipv4">Detecting...</span> </p> </div> <div class="ip-address-details-inline ip-address-ipv6"> <p id="ipv6-head" class="public-ipv6-address"> My Public IPv6<!-- --> : <span id="ipv6">Detecting...</span> </p> * https://www.whatismyip.com https://www.whatismyip.com The "Detecting" is replaced by JavaScript (see "commons-[hash].js") that goes out and tries to hit some hostnames: $ dig +short -t a api.whatismyip.com 34.117.39.86 $ dig +short -t aaaa api.whatismyip.com $ dig +short -t a apiv6.whatismyip.com $ dig +short -t aaaa apiv6.whatismyip.com 2600:1901:0:d110:: > T-Mobile in the United States was running out of IPv4 addresses and needed an IPv6 transition strategy. Their solution was 464XLAT and IPv6-only. * https://www.internetsociety.org/deploy360/2014/case-study-t-mobile-us-goes-ipv6-only-using-464xlat/ https://www.internetsociety.org/deploy360/2014/case-study-t-... The fact that some services on the Internet are (sadly) IPv4-only means they had to use a technology to allow connectivity, which is why you're seeing an IPv4 address: it's not on your handset but the translation box. Also, I simply menion T-Mobile as one example, but given they have 32% marketshare in the US: * https://www.statista.com/statistics/199359/market-share-of-wireless-carriers-in-the-us-by-subscriptions/ https://www.statista.com/statistics/199359/market-share-of-w... that means that one-third of all Americans with (smart)phones are using IPv6-only, without being allocated an IPv4 address, everyday: 125 million people. Verizon Wireless has a similar situation: > Verizon Wireless proactively deployed IPv6 even though they had an existing IPv4 network. Per reports, they had at least 70 internal instances of the same private address space, and found themselves spending effort and money on the resulting network complexity; IPv6 deployment was a solution that simplified their network and reduced the cost of operating it. Over 80% of traffic from Verizon Wireless to major online content providers now uses IPv6. * https://www.internetsociety.org/resources/2018/state-of-ipv6-deployment-2018/ https://www.internetsociety.org/resources/2018/state-of-ipv6... They initially (2014) had private IPv4 addresses on handset and NAT44ed them: not sure what they're doing in 2024. So that's another ~125 million people. 250 million people using something daily would qualify as a thing being "ready" in my mind.