Nice! Perhaps a Gibson quote is appropriate here:<p>> Program a map to display frequency of data exchange, every thousand megabytes a single pixel on a very large screen. Manhattan and Atlanta burn solid white. Then they start to pulse, the rate of traffic threatening to overload your simulation. Your map is about to go nova...
I don't think straight hilbert curves:IP ranges are the best mapping, and would prefer something built around ping times or hop check routings in 3 dimensions. Or integrate it with geolocation data. But! It's still super useful. Or integrate it with geolocation data.<p><i>On top of all of this, I also did a bonus scan of a few APNIC IP blocks every 30 mins for 24 hours. The data from that allows you to see the internet “breathe” as clients come online in the morning and offline at night</i><p>Really, I'm surprised there isn't a distributed/crowdsourced system to do this all the time and allow people to study the 'weather' in the datasphere.
Also for fun, ipv6 exhaustion counter.<p><a href="https://samsclass.info/ipv6/exhaustion-2016.htm" rel="nofollow">https://samsclass.info/ipv6/exhaustion-2016.htm</a>
I wish this used a good color mapping, like Viridis or cubehelix, or at least used HSLuv or HPLuv to map the parameters to colors. I bet we could see a lot more patterns in this then.<p>Edit:
I made a github issue for this:<p><a href="https://github.com/measurement-factory/ipv4-heatmap/issues/2" rel="nofollow">https://github.com/measurement-factory/ipv4-heatmap/issues/2</a>
I did something similar few years back, mapping ipv4 address space owners.<p><a href="http://zokier.net/stuff/map_of_the_internet.png" rel="nofollow">http://zokier.net/stuff/map_of_the_internet.png</a>
You can scan the whole internet in about an hour. I had luck using AWS and zmap.<p><a href="https://github.com/zmap/zmap" rel="nofollow">https://github.com/zmap/zmap</a>
According to [1] IPv6 adoption is slowed down significantly, so we stick to NAT for a decade at least I think.<p>[1] <a href="https://www.google.com/intl/ru/ipv6/statistics.html" rel="nofollow">https://www.google.com/intl/ru/ipv6/statistics.html</a>
The 9MB PNG is unoptimized. By passing it through optipng and advdef I managed to losslessly squish it down to 7MB.<p>Also, I would be remiss if I did not point out that this:<p>cat ping.txt | pcregrep -o1 ': (\d+\.\d+\.\d+\.\d+)'<p>is a Useless Use Of Cat.[1]<p>It should be rewritten:<p>pcregrep -o1 ': (\d+\.\d+\.\d+\.\d+)' <ping.txt<p>[1] <a href="http://porkmail.org/era/unix/award.html" rel="nofollow">http://porkmail.org/era/unix/award.html</a>
How do the number of internet connections relate to the number of nodes? Building fat pipes is not the answer just as more highways is not the answer to more destinations. The increase in traffic will consume more resources exponentially (factorially?)faster than the increase of address space
IPv6 Active Webhosts Hilbert also exist based on Akamai data as I found this d3 block by Vasco Asturiano:<p><a href="https://bl.ocks.org/vasturiano/0c0f60cf193fa3a04b5d414aed6f5834" rel="nofollow">https://bl.ocks.org/vasturiano/0c0f60cf193fa3a04b5d414aed6f5...</a><p>The author also has some other cool d3 visualizations of IPv6 Routes, AS, as well as IPv4 allocations.
It strikes me that we've "run out" of IPv4 address space but there's entire large blocks of space allocated to entities that don't appear to be using them.