Datacenter Watch: 2006-11-09

[reseller]

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

I guess I must change my bad habit of checking DCs before going to bed :-)

And I just wonder why those youngsters at Googleplex keep tinkering with the DCs. Don't they have better things to do?

Look what they have done to the following DCs:

[64.233.183.99...]
[64.233.183.104...]

[66.102.9.99...]
[66.102.9.104...]

[66.102.11.99...]
[66.102.11.104...]

[216.239.59.99...]
[216.239.59.104...]

And as usual, please check your keywords /key phrases and see whether you still exist on Google Planet.

PS. However the above DCs are still what I consider "affiliate programs friendly".

[edited by: tedster at 9:17 am (utc) on Nov. 10, 2006]

[reseller]

Hi Folks

Matt Cutts has graciously posted on his blog a very informative post dealing with both "Data Push & Data Refresh"

Explaining algorithm updates and data refreshes [mattcutts.com]

Thanks Matt. Highly appreciated.

[Tinus]

Hi Reseller,

Thanks. Always good to have a confirmation from Matt. I am a little puzzled about that last sentence of his post: "that particular data is being refreshed ". What does he mean with PARTICULAR DATA. Seems like there are different kind of data refreshes. Or is a data refresh search string related or so? Or can a filter be part of a data refresh?
Nice problem to think about under the Christmas tree.:)

[reseller]

Hi Folks

I see a new wave of movements on all the DCs, and changes in rankings of the pages/sites I watch.

Depending on the extent of changes that the new wave would bring, we might decide whether its a new "data refresh" or just a fix for the "bad data push" of the 20 Dec 2006.

Btw, from the tower of Google Datacenters Watch:

HO..HO..HO :-)

[LiGhTenn]

< this post was moved here from another location >

Ok... Well been using <an online datacenter tool> a bit more often this x-mas.

I seen a MASSIVE datacenter change at [64.233.167.104...]

I am super happy with this results droped down only from place 1 to place 2 . which is better then not showing at all.

according to this new Juggle please tell me how are you guys doing?

[edited by: tedster at 2:12 am (utc) on Dec. 29, 2006]

[g1smd]

The 64.233.169.nnn block of IP addresses are offline.

[centime]

@ g1smd

I mean to start tracking a couple of sites accross datacentre using a popular web based data center checker

I just wanna know, has data center watch ever falling foul or the google rule against using automated query software?

Do these data center checkers use google api?

or something similar

I mean , if I use a datacenter checker, I'll be dismayed if my sites suddenly nose dive

[g1smd]

Google has 46 Class-C blocks of IP addresses currently active; totalling more than 800 individual IP addresses.

I check results at less than 10 IP addresses, often just 2 or 3 IPs - but always all from different Class-C blocks.

Google usually has 2 or 3 different sets of results live at any one time, and often also has one or more IP addresses that are testing something out.

[reseller]

g1smd

Talking about check results. The following two "sets" of DCs, don't like at all Matt Cutts Backlinks at the moment :-)

[64.233.167.99...]
[64.233.167.104...]

For example:

link:www.mattcutts.com/blog/ [64.233.167.99]
link:www.mattcutts.com/blog/ [64.233.167.104]

And

[72.14.203.99...]
[72.14.203.104...]

For example:

link:www.mattcutts.com/blog/ [72.14.203.99]
link:www.mattcutts.com/blog/ [72.14.203.104]

Oh well. May be the above DCs are already dead :-)

[g1smd]

Those datacentres that currently give zero results for link:www.mattcutts.com/blog/ give plenty of results for link:mattcutts.com/blog/ instead...

[reseller]

g1smd

Yes. While the rest of the DCs show results for link:www.mattcutts.com/blog/ too. Therefore I think they are "dead" ones or show "unique" behaviour at least ;-)

[g1smd]

Matt has mentioned many times (in his blog) that he has flipped the preference for his site from www to non-www, and back, several times in the last year in webmastertools....

I assume that some datacentres are showing a delayed response to those requests.

[reseller]

The other possibility might be that the said two sets DCs have been "deserted".

[reseller]

Hi Folks

Just updating the thread ;-)

Today Matt Cutts has graciously posted [mattcutts.com] on his blog very interesting info regarding two sets of DCs; 64.233.183.xx and 72.14.203.xx. THose two sets continue to show PageRank value from older infrastructure (than the new one BigDaddy):

I’ve mentioned before that some data centers (I believe 64.233.183.xx and 72.14.203.xx) continue to show PageRank values from a slightly older infrastructure. Not a big deal, but I wanted to mention it for the hard-core data center watchers so that they don’t get confused.