Not that it actually matters, but I've had 220.127.116.11/19 blocked in a client's htaccess for well over 2 years and my note says it was registered 03/2011. I've often seen the original registration date changed when the info is updated.
FWIW - whois.domaintools.com also says AS33387 DATASHACK - DataShack, LC (registered Mar 18, 2011)
9:53 pm on Feb 4, 2014 (gmt 0)
Actually, the entire 107.150. range was re-registered/appointed during 12/2013.
Not that it matters. :)
10:37 pm on Feb 4, 2014 (gmt 0)
Yup, that's what I said :)
I've often seen the original registration date changed when the info is updated.
10:39 pm on Feb 4, 2014 (gmt 0)
keyplyr, are you positive your notes aren't attached to some type of time machine? I've still got huge slabs of 107 labeled bogon, including most of 144-191 with isolated holes. (Almost all of the holes are block-on-sight server farms. Figures.)
12:50 am on Feb 5, 2014 (gmt 0)
Found one I had no info on, not a new register, but new to me: Netelligent Hosting Services (Montreal) 18.104.22.168 - 22.214.171.124 126.96.36.199/19
Wearing UA "c3.sh/0.01" which I have not seen before.
1:15 am on Feb 5, 2014 (gmt 0)
@lucy24 did you look at the source I gave?
2:00 am on Feb 5, 2014 (gmt 0)
Thought I had HP fully blocked, but today 15.126.240.nnn displayed identical behaviour to those hyperactive Swedish fellows, xeex, et al... Make your own minds up. For me 188.8.131.52/8 is now Blocked
2:01 am on Feb 5, 2014 (gmt 0)
Fer hevvins sakes, I'm not saying you're wrong. Just that you seem to get a lot of retroactively correct information, which is unnerving :)
2:25 am on Feb 5, 2014 (gmt 0)
4:04 am on Feb 5, 2014 (gmt 0)
Mention of Bogons is relevant.
I had to contact two site hosts recently because I couldn't access their sites.
The first one took some time to resolve.
It was my national Asian ISP, who had used a Bogon IP (quite legitimately) in relaying, but the host-site had not updated their Bogon filter.
The second incident: Took me three months to get the CTO's attention, (whilst being fobbed-off by their Indian call-centre).
I'd guessed the same precipitating cause.
The guilty party this time was a major UK utility company using an old Bogon filter, until I nudged them to update it.