Google Datacenters Watch 2006-02-21

Observations, Analysis and Remarks

[frakilk]

< continued from [webmasterworld.com...] >

Current BigDaddy status from what I can see:

- BD is visible on (using 'sf giants' test)
64.233.161.99
64.233.161.104
64.233.161.105
64.233.161.147
64.233.171.99
64.233.171.104
64.233.171.105
64.233.171.147
64.233.179.104
64.233.185.104
64.233.187.104
66.249.93.104
216.239.37.99
216.239.37.104
216.239.39.99
216.239.39.104

That is around 1/3 of datacenters listed on the McDar tool (I think).

- For me at least BD is returning a significantly lower number of indexed pages.
- BD index is still clogged full of scrapers, doorways and 404s. Meanwhile the sites sticking by the guidelines are getting trounced.

Google puzzle me.

[edited by: tedster at 6:01 am (utc) on Nov. 8, 2006]
[edit reason] thread split [/edit]

[Miop]

< Miop,

are you all supplemental? >

No. I have two other all supplemental sites, and they have not even been cached since last August. I can't seem to persuade googlebot in, whatever I do.

[Hissingsid]

Hi,

Do we have a list of the live BD DCs?

These two appear to me (in my niche) to be giving results which I was seeing on google.co.uk and google.com default between mid January and mid February.
64.233.161.105
64.233.161.147

These three are giving what I hoped would settle down as the new BD results.
64.233.171.99
64.233.171.104
64.233.171.147

All 5 return giants.mlb.com at #1 for the search <sf giants>

Up until 2/27 all five were giving the results I'm now seeing on 171.99, 171.104 and 171.147.

I was feeling quite positive about BD, now I'm just confused.

Best wishes

Sid

[jenkers]

if the sf giants search is still valid then the following 'should be' BD DC's:

64.233.179.99
64.233.179.104
64.233.183.99
64.233.183.104
64.233.185.99
64.233.185.104
64.233.187.99
64.233.187.104
64.233.189.104
64.233.161.105
64.233.161.147
64.233.171.99
64.233.171.104
64.233.171.147
216.239.37.99
216.239.39.99
64.233.167.99
64.233.167.104
216.239.39.104
216.239.37.104

these others should be non-BD:

216.239.53.99
216.239.57.99
216.239.59.99
66.102.11.99
66.102.9.99
66.102.7.99
64.233.161.99
64.233.161.104
216.239.53.104
66.102.11.104
66.102.9.104
66.102.7.104
216.239.57.104
216.239.59.104
216.239.63.104
216.239.57.98
216.239.57.105
216.239.59.105
66.102.7.105
216.239.57.147
216.239.37.147
66.102.7.147
64.233.167.147

[angiolo]

My questions:

- Are the NOT "BD DC's" moving to "BD DC's"?

- Is this google behavior connected to google site-map? In other words: maybe Google is telling to webmaster to delete all "lost" pages, "garbages".

Maybe Google want to save space: they do not want to index "lost" page...

[maha]

BD results suppose to be moving non-BD over time. That's whole purpose of these data centers.

[angiolo]

You mean that in few weeks we will see only BD results everywhere.

Is it right?

[watercrazed]

That the plan, but I hope not the supplemental issue in current BD is a killer.

[Blade3]

On BD datacenter, my site appears at 19th page (10 results per page). But in Non BD datacenters, it is nowhere.

Anyone experienced similar situation?

[Liane]

For those of you worried about the supplemental issue, see DaveIFG's post here:
[webmasterworld.com...]

This thread was supposed to have been to discuss Big Daddy Observations, Analysis and Remarks but seems to have been hijacked for discussion of the "supplemental" issue only.

[Wibfision]

BD has taken over the 72.14.207.104 data centre now, which is my google.co.uk.

[Wibfision]

Ah it's changed back. 72.14.207.104 is switching back and forth between BD and not BD.

Anyway, I'm going to get a life and stay away from the computer for a while.

[UK_Web_Guy]

72.14.207.104 has been pretty solid in serving me BD results all day.

I think this is actually quite significant as it is 72.14.207.104 that has been serving my google.co.uk results for 90% of the past few weeks

< continued at: [webmasterworld.com...] >

[edited by: tedster at 6:53 am (utc) on Mar. 6, 2006]