| 11:27 am on Mar 17, 2006 (gmt 0)|
Just did a search on 220.127.116.11 to look if its BD. And it shows for
#1: sanfrancisco.giants.mlb.com/ NASApp/mlb/index.jsp?c_id=sf
is that new? All other DCs still show
| 11:37 am on Mar 17, 2006 (gmt 0)|
I guess the SF Giants site got changed. All the BD DCs will probably change to that url in time - which would be the correct thing to do.
| 11:38 am on Mar 17, 2006 (gmt 0)|
u are right. Its a redicrect to the new url.
So this must be an very up to date DC for BD?
Edit: Ok it just spread out to 18.104.22.168
| 4:31 pm on Mar 17, 2006 (gmt 0)|
I have one client (out of a couple hundred) who just completely tanked on March 8th - went from having been in the top 3 SERPS for most of their key phrases (for YEARS) to not showing up in the first 300. Their traffic (on a 4800 page static - not dynamic - site) is now 35 to 50% what it was on March 7, and orders have dropped off more than 50%. They haven't lost PR, nor the number of pages in Google, just position. The site is not overly SEO'd, in fact there's been very few changes to the layout or text in months, if not years. It's ALWAYS done well. They're considering layoffs now.
| 7:15 pm on Mar 17, 2006 (gmt 0)|
these were the unavailable DCs:
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
188.8.131.52 nicht erreichbar
184.108.40.206 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".
| 7:33 pm on Mar 17, 2006 (gmt 0)|
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%.
| 9:15 pm on Mar 17, 2006 (gmt 0)|
these were the unavailable DCs:
I was just curious, not sure what to do with dc's that are down
I have enough problems with the ones that are up,
I have contacted Google Help and boy were they helpful!
| 8:12 am on Mar 18, 2006 (gmt 0)|
Unwatchable BigDaddy Datacenters
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]
| 11:20 am on Mar 18, 2006 (gmt 0)|
> Take a look at these two BigDaddy Dcs and judge for yourself.
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?
| 4:07 pm on Mar 18, 2006 (gmt 0)|
"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 ;-)
| 5:18 pm on Mar 18, 2006 (gmt 0)|
some data centers are not responding, which means to me that BD is being rolled out further (if not completely)... we love BD!
[edited by: tedster at 9:18 pm (utc) on Mar. 18, 2006]
| 5:19 pm on Mar 18, 2006 (gmt 0)|
Correction on that last post... BD HAS been rolled out further... the old index is almost completely gone!
| 8:07 pm on Mar 18, 2006 (gmt 0)|
When I search for "Amazon" why does the book page show up first?.
| 8:56 pm on Mar 18, 2006 (gmt 0)|
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.
| 10:41 pm on Mar 18, 2006 (gmt 0)|
"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 ;-)
| 10:46 pm on Mar 18, 2006 (gmt 0)|
List of Google Datacenters
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!
| 10:59 pm on Mar 18, 2006 (gmt 0)|
Serps have been full of irrelevant/404/redirect/no links crap for almost two months. Google search is now knocking hard at death's door.
| 11:58 pm on Mar 18, 2006 (gmt 0)|
Why do you (or anyone else) never list 220.127.116.11 and 18.104.22.168?
After all 22.214.171.124 has been the main default DC for quite a long time now.
It currently switches from old default to Big Daddy on a few refreshes.
| 12:51 am on Mar 19, 2006 (gmt 0)|
126.96.36.199 -- Isn't giving me as many results as normal google or some of the 99's and 200's listed a few posts above..
| 4:14 am on Mar 19, 2006 (gmt 0)|
188.8.131.52 - seems to be my default here in northern Nevada.
| 4:40 am on Mar 19, 2006 (gmt 0)|
My default in Wisconsin is 184.108.40.206
| 5:30 am on Mar 19, 2006 (gmt 0)|
220.127.116.11 - is the only one out of about 10 DC's i checked showing good fresh results for me, everything else is back from oct/nov. not optimistic here, but patiently waiting.
interestingly, i don't see 18.104.22.168 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.
| 5:55 am on Mar 19, 2006 (gmt 0)|
I agree with the 72.14.207.... post..
but try this one:
This is currently what I see out of the Northwest (US)..
I like the results on the 72.14.207.... series better .. but I'm not the one rotating IPs through to the live index...
| 6:11 am on Mar 19, 2006 (gmt 0)|
Good morning Ellio
Why do you (or anyone else) never list 22.214.171.124 and 126.96.36.199? "
But I have included in the list the two DCs you mentioned .
Guess you need one or two Danish brand Cappuccino :-)
| 6:20 am on Mar 19, 2006 (gmt 0)|
"188.8.131.52 - seems to be my default here in northern Nevada."
"My default in Wisconsin is 184.108.40.206"
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?
| 7:14 am on Mar 19, 2006 (gmt 0)|
BigDaddy on 85% of Google Datacenters.. What then?
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?
| 7:23 am on Mar 19, 2006 (gmt 0)|
When Big Daddy is successfully deployed, Google will put their new infrastructure to work and start cleaning up the problems they said they would with their data set. My wish list: 301/302 misfires vanishing; clarity about who is scraping, who is re-publishing, and who is actually authoring; canonical problems of all kinds shrinking down to minimal.
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.
| 7:29 am on Mar 19, 2006 (gmt 0)|
decaff, 220.127.116.11 is showing old results for me.
| 8:05 am on Mar 19, 2006 (gmt 0)|
20 miles and 1500 vertical feet above icedowl we're also getting 18.104.22.168 as the default.
I'd agree with tedster but I'd like to also wish for more sunny powder days with lots of automatic deposits.
and backrubs with happy endings. :)
| 9:36 am on Mar 19, 2006 (gmt 0)|
Anybody grasped the significance of Mr Cutts' latest posting? 22.214.171.124?
Doesn't do anything for me. Can't find any data on the ip.
Maybe he's just messing with our minds
Maybe mine hasn't had enough caffeine yet this morning!
| 9:48 am on Mar 19, 2006 (gmt 0)|
I am trying to stay omptomistic too - it does looks like we will have to wait for full roll out before anything significant though.
That 72 set of dcs doesnt get mentioned enough as it is not on a lot of tools.
DCs which are not Big Daddy IMO are:-
Also showing Non Big Daddy results - but sometimes showing XML Big Daddy are :-
I guess they will be next to go Big Daddys way.
| This 210 message thread spans 7 pages: < < 210 ( 1 2 3 4  6 7 ) > > |