| 9:32 am on Oct 4, 2006 (gmt 0)|
Actually, I'm looking at 220.127.116.11 in the UK and it looks a lot better to me now.
I guess this isn't finished yet!
| 10:31 am on Oct 4, 2006 (gmt 0)|
"Actually, I'm looking at 18.104.22.168 in the UK and it looks a lot better to me now"
Must agree that that data centre does look good. However, im being served 22.214.171.124 in the midlands currently which is not so good. May i ask what part of the UK you are in to be served by that data centre?
| 12:54 pm on Oct 4, 2006 (gmt 0)|
Hi Rich, I'm Northumberland, right on the English / Scottish border.
126.96.36.199 has the latest PR readings too.
| 2:59 pm on Oct 4, 2006 (gmt 0)|
Is there a definitive Google DC list? I have checked every one that I can find in there forums, and I find our site listed pretty much exactly as it was before ranking around #4 to #6 (depending on DC). When I just go to google.com and conduct the same search (not knowing what dc I am getting) the results are very different and show us nowhere to be found.
I am just asking for a list of all google dc ip addresses so that I can try to make sense of what is happening.
| 3:13 pm on Oct 4, 2006 (gmt 0)|
never mind my previous post. I did a search in google for webmasterworld.com google data centers....
boy was that scary....
| 2:50 pm on Oct 4, 2006 (gmt 0)|
System: The following message was spliced on to this thread from: http://www.webmasterworld.com/google/3108195.htm [webmasterworld.com] by tedster - 11:16 am on Oct. 4, 2006 (EDT -4)
I seem to have lost most of my SERPS for one of my sites in the last update. What's odd is that I can't find a DC that duplicates the results I am getting on Google. All the DCs I check show the SERPs similar to what I have before the last update.
I've read through a good deal of posts regarding Big Daddy - [gfe-eh.google.com...] aka [188.8.131.52...] stating that the SERP's found there are what will be in Google moving forward(the SERPS look fine in these).
Can anyone shed some light on:
a) Is there a DC that shows the same results as Google.com
b) Are the SERPs in Big Daddy the future SERPs for google.com; and if so, is there an approximate propogation time for Big Daddy SERPs to show on google.com
| 5:30 pm on Oct 4, 2006 (gmt 0)|
I vote that "site:" isn't working properly on those dc's - if you search for unique content from pages which aren't listed in site: - you'll find they are indeed still indexed because they appear in the serps.
Applies to examples i've checked anyway.
| 6:21 pm on Oct 4, 2006 (gmt 0)|
1. No, there's no one data center that will always show you what you get on google.com. Google uses many ip addresses for ordinary google.com pages - and they can swtich data centers and/or ip addresses on a dime. They do this for load balancing or to test one set of results against others, or just because they can.
2. There's no IP address where you can be sure you are seing a preview.
Google Data Center IP lists [webmasterworld.com]
| 6:25 pm on Oct 4, 2006 (gmt 0)|
Went through the exhaustive DC list that g1smd et al put together and wasn't able to see similar results I get when I perform a search directly on www.google.com. I pinged google to get the ip address - and the SERPS that ip and www.google.com still don't match.
Anyway to determine/verify the ip address of www.google.com as the browser navigates to it?
| 6:32 pm on Oct 4, 2006 (gmt 0)|
thanks for the reply. As I mentioned, all the data centers I visited show the same results, except for www.google.com. What could be the problem? My results on Big Daddy are fine - Will they eventually propogate to www.google.com results?
| 7:59 pm on Oct 4, 2006 (gmt 0)|
rshandy: the BigDaddy update went on for months -- from 2005 October to 2006 March or more... but it's all over now.
For at least the past 3 or 4 months gfe-eh has given a rough indication of where we were heading, but about two weeks ago those results migrated to most of the other active datacentres.
>> Is there a DC that shows the same results as Google.com <<
Rather than access by IP address, try using the equivalent gfe-xx name instead.
>> Anyway to determine/verify the IP address of www.google.com as the browser navigates to it? <<
Upgrade your web browser to Mozilla, or Firefox, or Seamonkey, and then get the ShowIP extension from L4X.org too.
| 8:51 pm on Oct 4, 2006 (gmt 0)|
g1smd: Thanks very much. Your posts are very insightful. I went back to the DC list and checked the serps using the -gfe-xx nomenclature.
This is what I found.
SERPs were fine except for the following DCs:
gfe-bx, bx2, bx3
Are any of these DCs individually significant to determine which way the SERPs are proprogated from one DC to another? Or should I just monitor the DCs to see how the SERPs are changing.
Not sure how I affected the results as I have not changed anything on the site. I do show 4 pages as supplemental results, however...
| 9:05 pm on Oct 4, 2006 (gmt 0)|
Good evening Folks
Datacenters Watch ..Fun time
First take a look at this one [184.108.40.206]
And now for some Google Magic! [220.127.116.11]
| 9:16 pm on Oct 4, 2006 (gmt 0)|
Oh yes! I see that effect from time to time.
Results 1 - 3 of about 770 -- with no link to any more results...
Let's hope that Matt gets to see that one for himself.
That's one of those DCs showing recently with "result 4 onwards as Supplemental", or in this case "totally missing".
My guess is that the newer data (seen on all the other DCs) really is missing from those servers.
| 9:43 pm on Oct 4, 2006 (gmt 0)|
Thanks again g1smd! I'll post the results as soon as I see changes in the DCs.
| 9:51 pm on Oct 4, 2006 (gmt 0)|
g1smd - For what it's worth, I'm just seeing updated caches on those pages that had been rolled back.
| 10:07 pm on Oct 4, 2006 (gmt 0)|
They have either taken that DC offline (and temporarily routed all queries to some other), or updated it in the last few minutes, as that effect is no longer seen.
| 10:16 pm on Oct 4, 2006 (gmt 0)|
> Let's hope that Matt gets to see that one for himself.
Seems he has in the past two hours. I see nothing obscure on resellers links.
Besides: I performed that site: command on 18.104.22.168 for example. Weird result: 9 out of almost 900, four of which marked with a "300 Multiple choices" return, because the indexed/requested url was absolute nonsense (incomplete/wrong). My sitemap.xml is absolutely fine, so where the hell has google got this "page" or "link" from?
should I worry? the crawler had been trying to find and index pages like www.mydomain.com/myproductgroup/...gets.html
My first question is always: Have I made a mistake recently? Anything works perfectly fine on my default google-ip and I cannot find any mistake yet, so let me guess: THOSE THREE DOTS, do they have anything to do with some illformed handling of subdomains on the crawler's side? Or is it because I currently abuse Frege's "Begriffsschrift" as a mouse-pad?
| 10:39 pm on Oct 4, 2006 (gmt 0)|
gs1md, yes, also the site: command on 22.214.171.124 seems to work fine, but on the very last result page (results 841 - 847 of about 877) I again see that obscure dot notation. I found that some where listed as unavailable in my webmaster central sitemaps account.
| 11:33 pm on Oct 4, 2006 (gmt 0)|
A high number of key static pages are still missing. Previously at the top of site:, now nowhere to be seen, not showing up for their keywords anymore, anywhere - 0 google traffic to them.
| 11:51 pm on Oct 4, 2006 (gmt 0)|
LOL. Recently seen on [126.96.36.199...] ....
"Web Results 1 - 100 of about 0 from *********.com for ...."
...and then shows 100 results on first page (7th onwards Supplemental) and in theory there are 10 pages of results.
| 12:00 am on Oct 5, 2006 (gmt 0)|
Some of my internal pages had a inflated PR (ie higher than the homepage) after the recent update. At the moment - it seems as if the DCs are dancing to readjust the PR on these pages - zeroing them.
EDIT - Actually I'm seeing some sort of rollback on my new sites?
| 12:16 pm on Oct 5, 2006 (gmt 0)|
g1smd: just checked the "bad" DCs and all of them have propagated to the good SERPs. Thanks again for your help!
| 12:47 pm on Oct 5, 2006 (gmt 0)|
I am still seeing the broken site: command moving to other datacenters, hope they get this fixed soon
| 12:50 pm on Oct 5, 2006 (gmt 0)|
yep it's propagating :'(
It's quite worrying even though I can't see any traffic drop yet
[edited by: Frederic1 at 1:01 pm (utc) on Oct. 5, 2006]
| 1:06 pm on Oct 5, 2006 (gmt 0)|
Thanks for posting the link to the data centers back on page 4 of this particular topic.
I am now seeing results on google.com that very closely resemble [188.8.131.52...] with the exception of the last three serps on the first page of 10 results. I am sitting at #7 on both pages for 313,000,000 results on 184.108.40.206 and 324,000,000 on what I receive as google.com
| 2:56 pm on Oct 5, 2006 (gmt 0)|
Ya dont sese any changes in ranking, just showing all old urls that have been deleted and everything on every site i check is supplemental. On most datacetners now
| 3:28 pm on Oct 5, 2006 (gmt 0)|
I am being served results from 220.127.116.11
| 10:49 pm on Oct 5, 2006 (gmt 0)|
Good evening Folks
See what they have done to my baby DC (:(
More Google Magic [18.104.22.168]
Talking about "tinkering". I just read on Matt's blog the following comment [mattcutts.com] :
You guys need to quick tinkering and fix Google. Iím seeing more and more legit non duplicate pages go supplemental on larger sites. Smaller sites donít stand a chance anymore.
I miss the Google of a few years ago.
Lately, it seems the Google Spere is cracking.
And this is coming from someone who drives around with a Google License plate frame on his car!
Good night and God Bless!
| 10:50 pm on Oct 5, 2006 (gmt 0)|
The site:domain.com search is well and truly broken.
It is now almost totally useless for resolving any canonical or duplicate content issues with your site.
Well done Google!
If this continues, then you can disregard everything I wrote about using various Google searches to resolve Duplicate Content and Supplemental Results in the last two years.... Move along now. Nothing to see. Nothing that makes any sort of sense anyway.
| 2:29 am on Oct 6, 2006 (gmt 0)|
Perhaps this is just the darkness before the dawn.
| This 175 message thread spans 6 pages: < < 175 ( 1  3 4 5 6 ) > > |