AWS to charge customers for public IPv4 addresses from 2024
www.theregister.com
Perhaps that'll focus your minds on speeding up your adoption of IPv6, eh?

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.

    • HousePanther@lemmy.goblackcat.comEnglish
      15·
      1 year ago

      Verizon, my ISP, offers IPv6 in my area but the implementation is broken and it ends up being an order of magnitude slower than simply using IPv4 and HE as an IPv6 tunnel broker.

      • tychosmoose@lemm.ee
        5·
        1 year ago

        AT&T is the same. And the last time I looked they don’t give you enough address space to host your own subnet. You get a /64 instead of a /56. And it’s slower than ipv4.

        Every few months I try it out, complain and then switch it off.

        • Caaaaarrrrlll@lemmy.mlEnglish
          3·
          1 year ago

          I’m on ATT. I can get a /60 from their V6 router. I use /64s with each of my VLANs. I use a true bridge mode that bypasses their gateway device only using it for eap authentication. My router handles the connection. It works great honestly. Not sure what you mean by it being slower than V4. The V6 is equally as fast if not faster, here in Dallas. The routes are great on both V4 and V6, it takes on average 4 hops for me to reach the rest of the Internet. It’s about 1-3ms RTT to city-local addresses over ICMP echo. Very stable, too.

          • tychosmoose@lemm.ee
            2·
            1 year ago

            Interesting. In NC here. Not sure if there’s a difference regionally. I was seeing that kind of RTT on ipv4, but ipv6 was slower. I’ll need to give it another try. The last time I did was at my last place where I had the BGW210. I have the BGW320 now and haven’t tried on that. Maybe that, or changes in their routing since then will make a difference.