I discovered a humorous bug in the ripe whois database. If you search for something that should be unallocated in the range between 184.108.40.206 – 220.127.116.11 you will always get a /24 network in Kaliningrad, Russia as the response. Try 127.0.0.1 for example or the unallocated block 18.104.22.168.
This messed up my calculations earlier today. They underlying logic assumed that all IP-addresses in the range were allocated and removed those block from the free pool. I have fixed the problem for now.
Here is the link to the www version of whois. http://www.db.ripe.net/whois
Ripe is based in Amsterdam, NL
Update May 18 I emailed RIPE about the problem and got a reply that they now have fixed it.