I’m sure everyone is aware of the ever decreasing amount of IPv4 addresses left unallocated. Basically there’s 7 billion people on the planet, but only 4 billion IP addresses. Unless people start turning off their routers and whatever else when they’re not being used, IPv6 is going to be needed fairly quick.
RIPE recently allocated the 1.0.0.0/8 and 27.0.0.0/8 space of addresses out to APNIC. With that move, over 90% of the IPv4 address space has been assigned. In a normal day-to-day environment as a network engineer, most people will configure 1.1.1.1 as the loopback on a router to do some testing. Other people use it as their pseudo RC1918 range to avoid overlapping. Hell, it’s even used as the ‘internet range’ in alot of Cisco documentation.
In what seemed to be to check on the pollution (how many people were using the range), RIPE NCC decided to announce some of the ranges in the 1.0.0.0/8 range. These were:
1.255.0.0/16
1.50.0.0/22
1.2.3.0/24
1.1.1.0/24
Keeping in mind, RIPE never expected this to be a clean prefix. In the past they had done some tests announcing various 1.0.0.0/8 ranges, however they’d never done 1.1.1.0/24 before. What they saw a few minutes after announcing the range was incredible however:

The traffic incoming basically jumps from 3MB/s to over 9MB/s, maxing out the link they had assigned for the testing. You would hope that your webhosting provider in Australia isn’t assigned any address space in that 1.1.1.0/24 block, otherwise you might be in for a large excess traffic bill. Unless the traffic sent towards that address space is somewhat reduced, it can’t be used in a production environment.
Come on IPv6!