Welcome to WebmasterWorld Guest from 188.8.131.52
Looks like more Datacenters have been updated to Big Daddy. I am seeing lots of traffic from 184.108.40.206
My new sites are getting tons of traffic from google.com today.
[edited by: tedster at 6:54 am (utc) on Mar. 6, 2006]
220.127.116.11 nicht erreichbar
18.104.22.168 nicht erreichbar
22.214.171.124 nicht erreichbar
126.96.36.199 nicht erreichbar
188.8.131.52 nicht erreichbar
184.108.40.206 nicht erreichbar
220.127.116.11 nicht erreichbar
18.104.22.168 nicht erreichbar
22.214.171.124 nicht erreichbar
126.96.36.199 nicht erreichbar
Worked fine until the 8th or 9th of March. There were always one or two unavailable in my list but at that date it got stuck already in line four, so I interrupted; until yesterday when I decided to let it run thru.
I must admit I'm a fan of that 64bit-theory so I suggest those DCs temporarily unavailable are the ones currently switched over to that new "architecture".
I did not intend to split hairs. Its just that I always understood the word update as a qualitative step in the process of google' search-results-improvements. Such steps are the logical opposite of continuity.
I agree insofar as indeed there seems to be more continuity and graduition at work. Maybe google has found new mathematical means to sufficiently estimate PR instead of performing iteration over the whole matrix.
All in all, I meanwhile believe that a substantial part of ranking-evaluation is now drawn from an analysis of user behaviour gathered by the toolbar. There's so many features that might play a role nowadays. I do watch these discussions sporadically, but my main emphasis lies on usability and the needs of my visitors and customers. Allegra, Jagger, Big Daddy, each of them seems to have inceased my visitor statistics by about 20%.
Good morning Folks
Those of us who are "blessed" with the gift of Google Datacenters Watching, may feel some kind of frustrations. It could be because of the pattern, or lack of the same, of current DCs in general and BigDaddy DCs in particular.
Maybe its about time that we Google Datacenters Watchers start studying the possibility of adopting to new mindsets!
We need to forget all about Google Dance and Classic Updates mentality. We should take in account all possibilities and do a fresh and free DCs watching.
Otherwise we wouldn't get anything out of watching the DCs other than whining, frustrations and unqualified guess.
Take a look at this thread and spend some time reading what our kind WebmasterWorld fellow members have posted of observations, analysis and remarks. Can't you see that BigDaddy is a mixture of everything! You name it and you will have no difficulity find it on BigDaddy which keeps changing all the time.
Do you tell me that its only the deploy of the new infrastructurer you see on BigDaddy DCs? C'mon you must be kidding or reading too much of our good friend at the plex Matt Cutts blog :-)
Take a look at these two BigDaddy Dcs and judge for yourself.
Wish you all a great weekend and God bless.
[edited by: reseller at 8:17 am (utc) on Mar. 18, 2006]
those few major keywords I regularly watch for my little niche are as stable as ever.
I don't really see the point in watching results on various DCs at all. What counts is the resuts given for a search on google.#*$!.
It has been suggested several times, that google might switch over to rotating DCs, giving slightly different result-sets on each. This would clearly bear the advantage, that any SEO-technique aiming at a specific algo must necessarily fail, and those "natural" pages will perform relatively stable on all or most DCs.
So what about a google DC-ping-watch-thread next time?
What IPs are returned pinging to www.google.xxx or toolbarqueries.google.com? Are there any regularities concerning time or location? Why do the values of the toolbar differ from the rk-values given by toolbarqueries.google.com? Has anyone ever made any little progress by watching DCs at all and if not (which I presume): when's the time to give up and get back to work again?
"Has anyone ever made any little progress by watching DCs at all and if not (which I presume): when's the time to give up and get back to work again?"
Maybe you find the answer to your question in my first post when I started this thread:
Or this one:
I hope this helps ;-)
maybe I must excuse: whenever there's "something going on in the serps" your thread is one of the first and most valuable I always look at.
Nevertheless, I sometimes find it quite frustrating to read thru all the postings, because generally the problems and frustation massively outnumbers the solutions. This is not good for my mental health;)
I don't see the point in watching DCs and praying this or that DC-result-set might some day come out as THE final "update:" I suggest that present state with everyday DC-flux might become normal for a long period of time. It would then be logical to switch over to a detailed and regular observation of these switches, investigating which result-sets are delivered by searching google (as most people do), when, where and if possible why.
I don't see the necessity to use internet tools for watching DCs. Lists of IP-numbers are available all over this place. If you don't find the time to dive into scripting, the easiest solution is a simple frameset, replacing 'google' by the relevant IP and adding your keyword in the query-sequence. But I assume you know this.
"Nevertheless, I sometimes find it quite frustrating to read thru all the postings, because generally the problems and frustation massively outnumbers the solutions. This is not good for my mental health;)"
Thats the "side effects" of Google Datacenters Watching. Few hours away from your monitor and a bunch of fresh air should help ;-)
FYI, I'm posting the .99 and .104 of Google DCs that I'm aware of.
If you know of any other .99 and/or .104 DCs which are not listed here, please be kind to post them. Thanks!
interestingly, i don't see 188.8.131.52 results in my local SERPS at home or at work. i have to punch in the IP to see the fresh results. I'm on east coast, us.
"184.108.40.206 - seems to be my default here in northern Nevada."
"My default in Wisconsin is 220.127.116.11"
Good morning to both of you. Thanks. I shall include in my next DCs-list update the .99 and .104 of the DC you mentioned. Which are at present BigDaddy DCs!
Anybody else know of more DCs which I haven't listed?
I see BigDaddy emerging victorious on almost all the DCs, except for the following 3 sets
The question now is; what will happen just after BigDaddy being deployed on the the above last "old" 3 DCs?
I would like to see this and the new infrastructure could give Google the tool they need to make it happen. I like to dream positive dreams.