5 ms·
I keep wondering what will happen on AWS or Google when available public v4 IPs run out/low... Start charging $15 per address?
by coding123 9y ago
I keep wondering what will happen on AWS or Google when available public v4 IPs run out/low... Start charging $15 per address?
- dsr_ 9y agoYes. Or some other scheme similar to that, where IPv6 allocations are free but IPv4 costs real money.
- briffle 9y agoGoogle already charges you for reserved IP's that are not in use in their cloud.
- coding123 9y agoSame with AWS, but I'm referring to in-use cost, just curious if that's coming...
- olq 9y agoWell they have already ran out and the big old companies have their own reserved ipv4 ranges. They even buy other tech dinosaurs for their reserved ipv4 blocks in the order of $10 per adress. [1] [1] http://www.gtri.com/how-to-buy-or-sell-ipv4-addresses/ http://www.gtri.com/how-to-buy-or-sell-ipv4-addresses/
- ghaff 9y agoAmazon bought up to half of MIT's /8 addresses.
- jcrites 9y agoMIT recently sold part of their IPv4 address space to AWS (the block 18.145.0.0/16): http://www.networkworld.com/article/3191503/internet/mit-selling-8-million-coveted-ipv4-addresses-amazon-a-buyer.html http://www.networkworld.com/article/3191503/internet/mit-sel... https://whois.arin.net/rest/net/NET-18-145-0-0-1.html https://whois.arin.net/rest/net/NET-18-145-0-0-1.html According to the IPv4 Market Group, prices per address have trended around $8 - $12 (prices vary by block size): http://ipv4marketgroup.com/ipv4-pricing-in-a-post-arin-runout-world/ http://ipv4marketgroup.com/ipv4-pricing-in-a-post-arin-runou...
- lumisota 9y agoThey already charge on AWS. The cost of 1 IP is built-in to the hourly cost, with extras and those attached to stopped instances charged explicitly.
- nodesocket 9y agoHas the price per elastic IP ever gone up though on AWS? I don't think so, but you'd expect price to rise over time as less addresses become available.
- Xorlev 9y agoEIPs only cost money if they're unattached. Otherwise they're free.
- nodesocket 9y agoThat's what I am saying, the cost of an unattached EIP has not gone up has it?
- moduspwnens14 9y agoI don't think so, but I do remember when unattached EIPs were free before they became not-free.
- coding123 9y agoWell technically they don't charge a different price if you have a public ip or only a private IP on an instance. However even if they factored in that some high % of all EC2 instances will have a public IP and that's "part of the cost" what I'm really asking here is if eventually that cost will be so significant that they actually need to raise instance prices solely because of the IP price. If that's the case, then it may make sense to lock the instance price down, and start charging for in-use v4 IPs, not just unused allocated ones. Let's say the next block of 1 Million IPs that AWS wants to buy from say, GE fails to go through, and AWS is looking at a pool of 500K IPs starting to shrink at the rate of 30k per day. The only way to ensure they don't run out would be to separate the price out and jack up the price considerably so they don't run out. What I'm saying is that at some point, WHEN the number of IPs that people want outpaces the number AWS (or Google or other cloud provider) can obtain from other companies, they will be forced to change something. What would be interesting would be to see AWS etc, to try to get their customers to migrate off IPv4 for administrative and back-office services since there really isn't a strong reason to have VPNs and SSH or RDP sessions backed by a v4 address.
- aidenn0 9y agoI've already seen VPS services that charge extra for ipv4.