New Softlayer IP Range

Just heads-up

[blend27]

This Softlayer IP Range is new for me.

OrgName: SoftLayer Technologies Inc.
NetRange: 108.168.128.0 - 108.168.255.255
CIDR: 108.168.128.0/17
OriginAS: AS36351
NetName: SOFTLAYER-4-11
NetHandle: NET-108-168-128-0-1
RegDate: 2012-01-06
Updated: 2012-03-28
Ref: [whois.arin.net...]


2 hits, about 4 minutes apart, from 108.168.148.194-static.reverse.softlayer.com using python-requests/0.12.1 as UA. Did not ask for robots.txt. Pages it went for are 2 clicks away from homepage, so seems like following a list of URLs.

[keyplyr]

Thanks blend27, I didn't have that one.

[levo]

Does this look complete?

50.22.0.0/15
50.97.0.0/16
66.228.112.0/20
67.228.0.0/16
74.86.0.0/16
75.126.0.0/16
173.192.0.0/15
174.36.0.0/15
208.43.0.0/16
208.101.0.0/18
108.168.128.0/17

[dstiles]

I have one more - a RIPE range:

50.22.0.0 - 50.23.255.255
50.97.0.0 - 50.97.255.255
66.228.112.0 - 66.228.127.255
67.228.0.0 - 67.228.255.255
74.86.0.0 - 74.86.255.255
75.126.0.0 - 75.126.255.255
108.168.128.0 - 108.168.255.255
159.253.128.0 - 159.253.159.255 (RIPE)
173.192.0.0 - 173.193.255.255
174.36.0.0 - 174.37.255.255
208.43.0.0 - 208.43.255.255
208.101.0.0 - 208.101.63.255

[levo]

Thank you! Most of it was based on your previous posts here.

[keyplyr]

I had a couple more but it looks like they're now owned by AboveNet and ThePlanet.

[blend27]

Thanks Guys.

Perhaps following deserves its own thread but, I just checked my list of ranges from above mention and found that I had 3 outdated ones that are now own by ATT & Rogers :(.

Jugging by the timestamp all 3 were added to my list in late 2007. Which brings an interesting topic that has been on my mind for quiet a while now.

How do you maintain your RANGES for farms, colos and such? I don't mean adding new ones.. but making sure old ones are still belong to the "perpetrators"...

[wilderness]

How do you maintain your RANGES for farms, colos and such?

Once a farm, always a farm ;)

"You may take the boy out of the country,
But, you may not take the country out of the boy."

[levo]

Softlayer and Theplanet had merged last year. BTW, I've stumbled upon ARIN's range lists. How reliable are those lists for blocking?

for Theplanet: [whois.arin.net...]
rackspace: [whois.arin.net...]

[dstiles]

Damn! That's another couple of hours lost tomorrow! :(

Thanks, though. Very welcome.

[dstiles]

A few there I didn't have. Thanks, levo.

Two ranges I do not know how to deal with. Last week was the first time I came across an ill-used ipv6 range and there were two in the lists you gave:

The Planet
2610:40:: - 2610:40:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF

Rackspace
2001:4800:: - 2001:4807:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF

Has anyone yet come across a solution to this that is NOT based on htaccess? That is, something that has to rely on a range such as we are used to with ipv4?

Is it just a case of converting the (eg) 2001:4800 by multiplying up (and if so what multiplier) as when one multiplies each ipv4 byte by 256? As yet I haven't got around to reading up on ipv6. Damn, more time! :(

[wilderness]

dstiles,
It's my understanding that your host server either has IPV4 or IPV6 functioning.

Both will not work.

Thus if IPV4 functions disregard the other.

[levo]

dstiles, I think you're looking for a 'range to IPv6 CIDR' converter? There are some online converters.

wilderness, AFAIK Apache does support dual stack mode, but I've never used it.

As for discovering IP ranges, whois information for IPs have ref links to the ARIN page, like 'http://whois.arin.net/rest/org/GODAD' On those organization pages, look for the 'related networks' links and you get a nice long list of IP ranges. Softlayer's list didn't have the RIPE range, but hey it's a starting point.

[wilderness]

AFAIK Apache does support dual stack mode, but I've never used it.

Don't believe that takes effect until the next version upgrade.

[zeus]

hmm what are we talking about here, im at softlayer, is there problems there, be cause I always was happy with there hosting.

[wilderness]

hmm what are we talking about here, im at softlayer, is there problems there, be cause I always was happy with there hosting.

The references here are to Softayer IP's being used to crawl websites and/or as a standard internet users provider.

It has no correlation with SoftLayer's hosting services, with the exception that those same hosting services are being denied crawling access.

BTW, just because your using a host for their services, doesn't mean you need to allow them a free pass to all the content of your website (s)

[dstiles]

Thanks for the info, guys. Appreciated. I'll look further into ipv6 to see if my IIS server is likely to receive anything in that format.

Also noted the whois syntax - thanks for that, too. Although the links initially given had a trailing /nets on the URL, which may be the definer for the way we need it. It certainly works for the GoDaddy example given (except, again, I have more ranges than arin does - NL, SG and AU).

[blend27]

hmm what are we talking about here, im at softlayer, is there problems there, be cause I always was happy with there hosting.

zeus, I have a thingy for SoftLayer....

Up until not long ago SoftLayer was one in top 5 of "$hit list" IP ranges.

Hosting scrapped content by other scrapers, MFAs, scraping attempts, SQL Injections...etc, u name it = they have it, still.

[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]

Just to name a few...