and another gets on.

[lucy24]

199.30.16.75 - - [08/Jan/2013:10:04:02 -0800] "GET /robots.txt HTTP/1.1" 200 620 "-" "msnbot/2.0b (+http://search.msn.com/msnbot.htm)" 
199.30.16.75 - - [08/Jan/2013:10:04:02 -0800] "GET /sitemap.xml HTTP/1.1" 200 3880 "-" "msnbot/2.0b (+http://search.msn.com/msnbot.htm)" 

... and your point is?

199.30.16.0/20 Microsoft. Didn't they just add a new range the week before last? Now here they are again with still another.

Yes, it's really only .16.0/20. I checked. 199.30.0.0/20 is Sara Lee. And as long as I was there, I looked up other recent visitors from the neighborhood. 199.30.80.0/22 is StumbleUpon; 199.30.228.0/22 is DomainTools.

199 is going to be another of those abominable ranges like 91 or 193 where you never know what's in the /22 next door. I am not looking forward to v6-thingie at all. There will be :: business with calculator :: 65536 times as many of them. :(

[lucy24]

:: bump ::

Don't know what MS's long-term plan for this, uhm, rangette is. But the latest batch of logs had them trying it out on msnbot-media. I was alerted by the huge number of requests for robots.txt from an unaccustomed quarter.

:: edit, edit, edit in log-wrangling function ::

bingbot and msnbot don't get the huge number of spoofers that googlebot does, but it's enough that I can't just wave in anyone who flashes a Bingbot ID. Well, I could. This isn't my day job. But I don't feel like it.

[keyplyr]

Didn't they just add a new range the week before last?

Really? What MS range was added week before last?

[lucy24]

All right, if you're going to be hair-splittingly technical, it was late June for the 131.253 range. :P It's got a thread of its own.

[keyplyr]

Thanks, but 131.253.21.0 - 131.253.47.255 has been on/off bot running for nearly 6 years (I added it for MS in March, 2007.) You had me wondering if I actually missed a new one.

note: I don't play tag with bots. If the range is owned by a major SE, I allow them to do anything they like except cache/copy my content (e.g. translators, transcoders, etc.)

However, I personally hadn't seen any bot activity from 199.30.16.0 - 199.30.31.255. Thanks for the heads-up.