Be careful with Linode. Not all ranges are servers.
10:00 pm on Nov 27, 2012 (gmt 0)
And PLEASE concatenate adjacent IP ranges! I usually compare IP lists posted here with my own blocked ranges, adding new-to-me ranges and reporting missed ones. That list is far too long and fragmented and would take far too long to check out.
For what it's worth, my current linode ranges, all blocked, are:
@dstiles. You are absolutely right about concatenation! I do the same thing as far as comparing goes.
In the past couple of month many of us started listing full range of IP Ranges belonging to a specific Colo/Hosting companies.
Perhaps it is time for a WebService... hint hint...
10:56 am on Nov 30, 2012 (gmt 0)
Just a FYI - in my area... Qualcomm, a law school and most libraries and city depts all use Linode for their connectivity to the internet (not for cloud servers.) After receiving a few emails from customers complaining they could not access my sites, I took down blocks to several Linode ranges.
I suspect a measurable amount of my sales come from employees during their work day. YMMV.
Always a gamble when these companies offer a diverse product line.
9:31 pm on Nov 30, 2012 (gmt 0)
The answer is in the hands of the IT people for the companies concerned. If they state in their DNS records the purpose of a specific IP range they will gain more respect and fewer complaints. Very few hosting companies do this; I've mostly seen it noted by DSL providers.
To give them their due, Amazon does at least state in their DNS records that ranges are used for dynamic (cloud) hosting.