Cloud giant AWS will start charging customers for public IPv4 addresses from next year, claiming it is forced to do this because of the increasing scarcity of these and to encourage the use of IPv6 instead.
The update will come into effect on February 1, 2024, when AWS customers will see a charge of $0.005 (half a cent) per IP address per hour for all public IPv4 addresses. … These charges will apply to all AWS services including EC2, Relational Database Service (RDS) database instances, Elastic Kubernetes Service (EKS) nodes, and will apply across all AWS regions, the company said.
IPv6 is already relatively widespread in the USA (and many other countries) on the client-side, especially on mobile networks.
The main issue is that a lot of sites aren’t available over IPv6. Hopefully Amazon helps push that along.
I have IPv6 connectivity through Verizon FiOS. The trouble is that in my area it is poorly implemented and markedly slower than IPv4. I would much rather use 6 but not at a performance penalty.
Ahh, that sucks. Sorry to hear. A proper IPv6 network should be faster than IPv4, since there’s no NAT and no complex routing rules.
Agreed! Also smaller packet sizes.
In Sweden we have just one ISP for non-commercial customers providing native IPv6 adresses (Bahnhof) on fiber connections, and even then we can’t get a static prefix from them.
Not quite sure on the mobile ISPs though.
It’s the same here in Finland. Only one provider (DNA) offers IPv6 for residential customers and others are “working on it” still.
At least Tele2 supports IPv6 on mobile, not sure about others
I guess that means able to access services on the Internet over IPv6, not me being able to get a /64 and providing services myself to others.
Sort of ok for phones I guess, although not as great if someone doesn’t have access to fiber and have to use a mobile link in a residential environment.
Bahnhof actually just provides NAT:ed fiber connections as well as default, but will issue a public, unique IP if asked (at no additional cost).