Toonk is the blog of a network engineer writing on internet routing, AWS IPv4 holdings, packet processing in Go and network performance.
HN links it for data on AWS's IPv4 address value, AF_XDP packet generation and throughput measurements; commenters often correct submitted URLs.
There is no shortage of IPv4 address space. There is a problem with the government and private entities hoarding address space they don't need.
Amazon alone is sitting on billions of IPv4 addresses. They've snarfed up /10's, /8's, and partial /8's: https://toonk.io/aws-and-their-billions-in-ipv4-addresses/index.html
Every single man woman and child in the US could get three unique IPv4 addresses each and Amazon would still have billions left over.
And then recently the DoD transferred 175M IPv4 addresses to a shell corporation in Florida nobody has ever heard of, an then that shell corp announced the largest # of IPv4 addresses in the world: https://arstechnica.com/information-technology/2021/04/pentagon-explains-odd-transfer-of-175-million-ip-addresses-to-obscure-company/
The whole "IPv4 space is exhausted" is a load of shit to get people to feel guilty about having a class C and downsizing while Amazon, Google, and Microsoft snarf up more and more IPv4 space. It's exactly like "turn off your lights when you leave the room to reduce your carbon footprint" while a billionaire flies over you in his private jet in a 20 minute flight to the beach because he didn't want to sit in traffic.
All this could have been avoided if a)address space could not be sold or "leased" but had to be returned to APIC b)rules regarding a minimum percentage of your existing address space being announced/routable with actual devices at the other end...before more space will be allocated to you.
I find this extremely hard to believe.
EDIT: Just to clarify, AWS has a lot of IPs, over 100 million [1]. Let’s just speculate that 1/50th might be in an overall pool for customer allocation. Do you really think the majority of 2M IPs would come back blacklisted in some form? I haven’t dug in to this to actually see if this is the case, but it would seem laughable to even begin to think that this might be the case..
[1] https://toonk.io/aws-and-their-billions-in-ipv4-addresses/index.html
correct, direct url is https://toonk.io/aws-ipv4-estate-now-worth-4-5-billion/index.html
More interestingly, perhaps, is a forward look at how much new revenue AWS will generate once AWS starts charging ($44 per IP per year) as of 2024. I think it's not unlikely that AWS will generate a few hundred million to a billion in additional revenue with this new charge.
The actual number is much higher. Amazon doesn’t publish all their IP addresses in that json, only the ones in use. They have almost double the IPv4 addresses, ie quite a bit reserved for future use. See https://toonk.io/aws-and-their-billions-in-ipv4-addresses/index.html
"SCION OSS border router performance reached a ceiling of around 400k-500k packets per second, which is roughly equivalent to 5-6 Gbit/s at a 1500-byte MTU." vs. 1.4 M PPS for IP (on an older CPU) https://toonk.io/linux-kernel-and-measuring-network-throughput/index.html
URL is currently showing as http://index.html/
Correct URL: https://toonk.io/ipv4-sale-wide-and-apnic-selling-43-8/index.html
I tried to re-submit with the correct URL, but it got erroneously canonicalized to the same thing and marked as a dupe.