Some Google hints

216.33.229.163 and Python again

[pontifex]

OK,

there were 2 posts in the past, a little older, but to be complete:

216.33.229.163 is part of the Google IPs, I found out, when I traced to 216.33.229.164...

the python url lib agent is the "slideshow" from the google labs.

Not sure, if that was mentioned here...

good n8!
P!

[JuniorHarris]

Huh?

ARIN [ws.arin.net] shows that address as belonging to a company out of Cary, NC.

[wilderness]

This thread related and there is still more in the archives.

[webmasterworld.com...]

[Key_Master]

hmmm, pontifex is onto something here.

[GeorgeGG]

Most all the address's between
216.33.229.1 - 216.33.229.127
with a hostname are lycos.com, lycosnetwork.com,
terralycos.com and quote.com/whowhere.com which
also belong to Lycos.

216.33.229.135 = rdns01.sntc03.exodus.net

Couldn't get anything on the rest of the block, .136-.255

[wilderness]

Using the "google viewer" on a search which returns 4 of the top 5 pages from two of my sites resulted in 4 duplicate entries in my logs.

216.239.33.5 - - [14/Jul/2003:08:25:14 -0700] "GET mypages.html HTTP/1.0" 200 16431 "-" "Python-urllib/2.0a1"

Is it "possible" in the initial inquiry that the 239 and 33 were reversed?

If so?
Google has the enire 216.239.32-63 block.

[pontifex]

if you do a traceroute to 216.33.229.164, you get:

traceroute to 216.33.229.164 (216.33.229.164), 30 hops max, 40 byte packets
1 xxxx (192.168.200.1) 1 ms 0 ms 0 ms
2 xxxx (xxxxxxxx) 1 ms 1 ms 1 ms
3 xxxx (xxxxxxx) 62 ms 61 ms 61 ms
4 xxxx (xxxxxxx) 62 ms 62 ms 61 ms
5 xxxx (xxx) 64 ms 62 ms 62 ms
6 fe0-0-13.Frankfurt-6.primustel.COM (195.35.0.77) 63 ms 63 ms 309 ms
7 FE1-0.pr1.fra.primustel.com (195.35.0.14) 64 ms 63 ms 64 ms
8 GE1-0-10.cr1.fra.primustel.com (195.214.102.2) 64 ms 64 ms 63 ms
9 a7-0.111.cr1-jfk.primustel.com (209.227.129.14) 147 ms 148 ms 148 ms
10 a7-0-202.pr2.jfk.primustel.com (209.227.128.193) 148 ms 147 ms 148 ms
11 iar4-so-2-1-0.NewYork.cw.net (208.173.135.177) 150 ms 151 ms 152 ms
12 agr1-loopback.NewYork.cw.net (206.24.194.101) 151 ms 151 ms 150 ms
13 dcr1-so-6-0-0.NewYork.cw.net (206.24.207.49) 151 ms 150 ms 150 ms
14 dcr2-loopback.SantaClara.cw.net (208.172.146.100) 238 ms 238 ms 237 ms
15 bhr2-pos-0-0.SantaClarasc3.cw.net (208.172.156.214) 239 ms 240 ms 238 ms
16 csr1-ve240.SantaClarasc3.cw.net (216.33.153.197) 238 ms 238 ms 239 ms
17 216.33.229.148 (216.33.229.148) 240 ms 238 ms 239 ms
18 * * *
19 216-239-45-4.google.com (216.239.45.4) 241 ms 240 ms 241 ms
20 216.33.229.164 (216.33.229.164) 241 ms 241 ms 241 ms

i X'ed my privat infos..., so this is Google... I included the IP block to my monitor list and now I get the python stuff again... googlebot and python are shaking hands from these IPs.

What is that? Any ideas?
P!

[wilderness]

P!

There are many possibilities.
One is somebody is participating in Google's Compute [toolbar.google.com]

Another just some more behind the scenes stuff related to Cable and Wireless ( line 16 of your tracert;216.33.153.197)

I don't care for the association with Exodus or Cable & Wireless.

I almost completely stopped using tracert some time back.
Thanks for waking me up :-)

Guess we'll just have to wait and see what google's or WHOEVER is up to?

BTW my own tracert on line 13, showed a 192.168.68.1 (black hole) before the last two tracert lines.

Don