Technology

37705 readers

289 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

150

AWS: IPv4 addresses cost too much, so you’re going to pay (www.theregister.com)

submitted 1 year ago by [email protected] to c/[email protected]

54 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 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.