Want IPv6...... please hold forever.
I specifically asked for IPv6 and was told they don't offer that.
The price keeps slowly going up, but that seems to be par for the course with ISPs.
That being said, the CGNAT thing is just silly in 2023 - give us IPv6.
But the real number (at least on mobile networks) may be closer to 20%: https://www.internetsociety.org/resources/2018/state-of-ipv6...
I'd assume that when you have IPv6, the majority of your traffic (in bytes) will be IPv6 simply because all the CDNs and big video services do support IPv6.
Once my router at home crashed in a way that IPv4 stopped working but IPv6 kept on working and it was actually kind hard to figure out what went wrong because so much of the internet still worked fine.
Obviously we couldn't subnet it back when we derived the last 64 bits from the MAC address. But since then everyone decided that's a bad idea, so why not use the address space?
If you pay for a business connection you can get 1 or more static IPv4 addresses, but then you get no IPv6 connectivity.
Literally one instance with VPC service endpoints deployed and an egress NAT gateway. Surprisingly common when you have a random shitbox which sucks data up from somewhere and doesn't fit within the constraints of a Lambda or something. They mostly exist to tick the compliance and architectural documents which are all under AWS "best practices".
Note that I do not consider AWS "best practices" to be best practices necessarily. In fact a lot of time they are completely over-engineered against hypothetical scenarios which if they did happen, fixing some EC2 integration shitbox would not even remotely be the first problem you had to worry about.
But someone demands it and someone pays for it and Bezos ain't complaining so meh!