It's embarrassing that the cloud providers weren't IPv6-capable from day one. They're new, not legacy systems.
EC2 is 10 years old
IPv6 is 18 years old.
However, most of the users of internet were not ipv6 ready until very recently. It is a simply supply and demand question, where nobody wanted to invest in ipv6 infra first. Replacing networking gear for supporting ipv6 is very pricey operation too. I remember having pretty bad issues of having a dual stack in software. One example is when the python resolver library defaulted to ipv6 resolution first for a domain name, and the nxdomain to the AAAA request invalidated the name cache on the servers. When we changed this behaviour to default to ipv4 we saved an insane amount of CPU time. There are lots of issues like this one in a cloud environment, most people are never going to face this though.
Verizon FIOS and DSL still doesn't provide ipv6 addresses, so we have a ways to go still.
IPv6 is pointless until we remove IPv4
We're sad about that, too (I work on Google Cloud).
While not a perfect solution, you can use CloudFlare in front of your app/site for full IPv6 support without having to deal with AAAA records and IPv6 support from your origin.
Yep - thats what we rolled out for our iOS app, CloudFlare IPv4/6 + AWS just IPv4
As I was told recently, IPV6 is not comming anytime soon to GCP (not in next 6 months).
I think Google internally uses ipv6 for desktop computers though. I thought they are going to be faster with ipv6 rollout given how much they are investing into SDNs.
I think they would make it public if they believe they are scale ready. From my experience working there years ago, one of the first requirements was to be able to scale to any kind of requirements.
Well most ISP don't support IPv6 so it's really not an issue atm.
The 2 largest ISPs in my area (and 2 of the largest in the US), AT&T and Comcast, both support IPv6.
You might be surprised. Almost every cable company in the US does, so most Internet users in the US could have ipv6.
The problem is usually the $50 wireless access point most people bought 5 years ago doesn't pass ipv6 through.
Spectrum (formerly TWC) in Dallas does not. I still run an he.net tunnel on my router.
Last time I checked (a few months ago), UVerse in Dallas didn't either.
I had IPv6 from TWC, then for a month or so before the merger it went MIA, and then about a month after the merger it was back. For some reason I get a more reliable path to my IPv6 gateway than IPv4, so I missed it quite a bit.
Spectrum/TWC has had IPv6 via DHCPv6 with prefix delegation for a few years in Louisville, but only with a select set of modems. A Juniper DOCSIS 3 wouldn't work for me while a Motorola had no trouble.
I wonder if it's a regional thing? A friend of mine has spectrum from Charter (formerly Bresnan in this case) and he gets ipv6.
Servers in different regions don't have to do double nat. You may not have this problem, but some people do. And it sucks.
Sure, if by most you ignore Comcast, Time Warner, Cox, T-Mobile, Qwest, Charter, Verizon....