| 9:57 am on Sep 25, 2006 (gmt 0)|
18.104.22.168 - gfe-kc
22.214.171.124 - gfe-kc2
These were active [webmasterworld.com] back in June and are still active now.
I believe gfe-eh to be sort-of where we are heading, and gfe-gv to be where we have been.
| 2:23 pm on Sep 25, 2006 (gmt 0)|
System: The following message was spliced on to this thread from: http://www.webmasterworld.com/google/3095950.htm [webmasterworld.com] by tedster - 11:34 am on Sep. 25, 2006 (EDT -4)
Just wondering if anyone else has noticed google's datacentres stabalizing a little? It was all over the board a few weeks ago, but now I don't see any difference among the 72's, 64's etc.
| 6:52 pm on Sep 25, 2006 (gmt 0)|
Now then. This is ODD. I'm missing something here...
Let me put some detail in first...
Several years ago, some pages of content were amended to remove a particular word from the page.
Google reindexed the pages and they continued to rank for various terms as normal results. There were also some duplicate content issues where the "exact" same pages were published on other domains, as well as there being several ways to get to some of the pages using slightly different parameters. Those all got amended too. The word was removed from all of them. Some of those URLs were marked up as Supplemental Results, and some were not.
After a while, most of the duplicate URLs vanished from the SERPs, but some stayed around.
If you searched for current content, you got a normal result, but if you searched for the "removed" word, you got the same URLs back, but this time as Supplemental Results. The "removed" word also appeared in the snippet.
After a year, Google dropped all those Supplemental Results and you could no longer find any evidence of the "removed" word on that site, or related sites.
That was more than a year ago.
Yesterday, some of those URLs are back in the index when you search for the "removed" word. The "removed" word shows in the snippet too. The "removed" word is NOT on the real site, and has not been there for about two years.
This is the kicker: The URLs are NOT marked as being Supplemental Results.
What is going on?
| 8:18 pm on Sep 25, 2006 (gmt 0)|
| 8:31 pm on Sep 25, 2006 (gmt 0)|
Only a few URLs from that time have reappeared.
Most have not. The majority remain "gone".
If it is rollback, then it is a very long way back. I have never seen anything go that far back before. Nowhere near.
However, it's the fact that the very old data is not tagged as Supplemental that interests me the most.
| 11:53 pm on Sep 25, 2006 (gmt 0)|
something IS brewing. I search for "mydomain.com" on a penalized site, and now it's not even in the top 100 (from the 30's.)
Also, now the page numbers are accurate, despite about half being supplementals.
| 5:59 am on Sep 26, 2006 (gmt 0)|
Seems like a rollback...I hope it wont last as things started to look better...
| 9:25 am on Sep 26, 2006 (gmt 0)|
126.96.36.199 is serving UK results at the moment - is this a new DC?
| 9:38 am on Sep 26, 2006 (gmt 0)|
this is the point. No matter what you observe or hope for old pages are never going to be removed from google. They may become hidden or tagged in a different way but as part of the algo takes into consideration the history of a page theres just no way old versions of pages will ever actually be removed. This is bad news where those pages are not just old versions but either incorrectly indexed or incorrectly duplicated pages. This includes canonical problems where you have both the www and non www of the same page indexed at any point in time past.
I also predict at some point a google version of the waybackmachine.
| 12:48 pm on Sep 26, 2006 (gmt 0)|
For may webmasters, google is already the "waybackmachine"
| 1:32 pm on Sep 26, 2006 (gmt 0)|
i was right then! :)
| 7:28 pm on Sep 26, 2006 (gmt 0)|
umm... its 27th here in India, anyone see a data refresh in the distance?
| 7:41 pm on Sep 26, 2006 (gmt 0)|
Forget a "Data Refresh" it's long long long past due for an "Update!".
| 9:13 pm on Sep 26, 2006 (gmt 0)|
Good evening Folks
I would say that the DCs are calm and somewhat relatively quite.
Maybe we have already witnessed a modern Google update a la "Smooth Operator" :-)
Well.. we shouldn't be surprised at all if that was the case. Uncle Matt The Cutts has indicated that we shouldn't expect ton of movements on the DCs ;-)
The sad side of all that is we aren't going to have in future updates where our Brett gives them specific names , unfortunately. I will for sure miss that.
| 9:17 pm on Sep 26, 2006 (gmt 0)|
Agreed. Having a good day with very stable results after several rankings in total chaos since 9/15.
| 9:21 pm on Sep 26, 2006 (gmt 0)|
|188.8.131.52 is serving UK results at the moment - is this a new DC? |
Nothing new under the sun of mighty GOOG :-)
184.108.40.206 is showing something like the results of [220.127.116.11...] at the moment, IMO.
| 9:28 pm on Sep 26, 2006 (gmt 0)|
Stable? I'm seeing movement for some sites I watch. I also see a slight supplemental change. It's like a few pages pop out of the supplemental index every day or so.
| 4:17 pm on Sep 27, 2006 (gmt 0)|
Its Google birthday today!
Don't know whether we can also consider the same date as birthday of all Google's datacenters. I assume so.
Happy Birthday To ALL Google's GREAT FANTASTIC datacenters including [18.104.22.168...] of course :-)
And of course a special reseller Google birthday song.
Oh Google.. You Are Simply The Best.. Better Than All The Rest!
| 9:12 pm on Sep 27, 2006 (gmt 0)|
Its over..I guess
It seems that we have to live with the serps of 72.14.207.*** for the near future at least. Because I see the new infrastructure DCs have been relatively quite during the last few days or so. The remaining movements mightbe only to see propagation of the the serps of 72.14.207.*** to the rest of the DCs, or most of them.
To those of you kind fellow members who are doing well on the current 72.14.207.*** ... congrats.
To the rest... lets wait and see what will happen at the end of October. Maybe another White Revolution, who knows ;-)
| 9:15 pm on Sep 27, 2006 (gmt 0)|
The new IPs [webmasterworld.com] that have recently come online have the same SERPs as 72.14.207.* so I guess that's it for now.
They wouldn't put old data on brand new machines would they?
| 9:33 pm on Sep 27, 2006 (gmt 0)|
|They wouldn't put old data on brand new machines would they? |
Of course not.
And now we may as well start the new period of very interesting datacenters watching :-)
And thanks for your great generous contributions to the thread, g1smd!
| 2:49 am on Sep 28, 2006 (gmt 0)|
Tonight's interesting DC watching is showing me that on some SERP's interior pages are ranking above homepages for large and well-established sites. Pretty funky but hopefully something that will be gone soon and will only be remembered when I tell my grandchildren about it.
| 4:05 pm on Sep 28, 2006 (gmt 0)|
To assume that a new set of IP address is a new datacenter, well we know what "assume" broken down into 3 words is. These new IP address could be a new nics added to existing boxes, or load balancers for additional bandwidth, or redundantancy for an additional path to a box or load balancer, or a range of reactivated ip address on existing load balancers that have not been used in some time.
With the possible complexities involved with infrastructure design, IP addresses mean very little, any external facing ip address can be routed to any internal ip address, anywere, and you would never know which boxes really return a response to a query.
Are you watching 50 plus datacenters, serving up 3-4 sets of results, or are you watching 50 ip address ranges for 10 load balancers that distribute to 4 different datacenters with different results, or are you watching 50+ ip address ranges for 20 load balancers with 100 datacenters throughout the world with a mix of 3-4 sets of results, and on and on, because any of these are possible, and can be rearanged on the fly, and you would never know.
Once again, this is IMHO
Back to watching.
| 4:54 pm on Sep 28, 2006 (gmt 0)|
WW_Watcher would you say, the only thing out there that might be static would be some MAC addresses? Even that is iffy if you know what I mean? ;).
[edited by: theBear at 4:59 pm (utc) on Sep. 28, 2006]
| 6:30 pm on Sep 28, 2006 (gmt 0)|
Hey thebear,, whats up, been a while.
"WW_Watcher would you say, the only thing out there that might be static would be some MAC addresses? Even that is iffy if you know what I mean? ;). "
Yes I would agree with that, (not normally changed for possible confict reasons), but anytime a nic failed, the IP address might not change, but the MAC would. Anytime a load balancer was replaced (with multiple nics) the IP address might not change, but the MAC would.
BUT back to the original issue, these are ip addresses on load balancers, probely not actual datacenters, I would expect every true datacenter (building full of boxes) would have many different IP ranges for load balancers facing the internet for us to see. With DNS smoke and mirrors finding the closest (fewest number of hops) to the datacenter nearest us, adding and removing ip addresses for load balancers at will. After your request has reached a load balancer, your request could be routed to a pool of more load balancers, picking the least busy one (based on number of connections, or traffic load, or CPU utilization) of which the least busy would then route your request to the least busy server in the pool. Each server in that pool, can also be a swimmer in another pool serving up responses out another load balancer. At any point during the routing between load balancers, they could choose to send your original request over to another totally different Datacenter(building full of boxes), within their network and you would never know.
To confuse it further, I would expect that each of the true boxes serving up responses to queries are load balanced possibly to other boxes that actually service the databases. So a single box that responds to a query could be asking that query to multiple databases, possibly with different data, or algo. The possiblities are endless, and only G knows for sure are they are setup at any given moment.
Now I am lost, confused and forgot what my original point was, I asked, but was given 3 different responses....
I'm better off watching (not the datacenters, time is better spent lately revewing what others have discovered about the current serps, and the making the changes reqired to properly instruct search engines in general how to view and index your site. As the real professionals have stated over and over(not me, I normally do not post anything, and as a "webmaster" I consider myself almost clueless, successful, but almost clueless))
| 9:12 pm on Sep 28, 2006 (gmt 0)|
System: The following message was spliced on to this thread from: http://www.webmasterworld.com/google/3101021.htm [webmasterworld.com] by tedster - 5:59 pm on Sep. 28, 2006 (EDT -4)
I suspect that there may be another update/shuffle/everflux coming this weekend - don't know why but I do...
What are the current data ceneters G is using and is "Big Daddy" still producing results?
Thanks in advance!
| 10:56 am on Sep 29, 2006 (gmt 0)|
The "end-of-summer Dc" is now all over the Dc's for the sector I watch.
I'm a bit disappointed with the serps, wich looks bad as usual.
Anyway there aren't relevant changes for what I can see.
Is it really all here the "big fat google update"?
Anyone can see a radical/minor change on google algo now?
| 2:50 pm on Sep 29, 2006 (gmt 0)|
el nino update is on its way
| 5:34 pm on Sep 29, 2006 (gmt 0)|
I am noticing well above average googlebot activity so maybe a real update is due soon.
| 9:57 pm on Sep 29, 2006 (gmt 0)|
"real update is due soon"
Well guys is it strange or is only me? Haven't you noticed yet that there is a major PR TB BL update spreading all over the DC's :>(?
| 10:07 pm on Sep 29, 2006 (gmt 0)|
|Well guys is it strange or is only me? Haven't you noticed yet that there is a major PR TB BL update spreading all over the DC's :>(? |
Sure. Would prefer something that actually matters, though.
| This 200 message thread spans 7 pages: < < 200 ( 1 2 3 4  6 7 ) > > |