Forum Moderators: Robert Charlton & goodroi
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]
At least 10% of the results suddenly have extra-long snippets. However, it is just the normal snippet repeated a total of two or three times.
Seen it mentioned before. Only seeing it for myself as of now. Currently geting results from: 216.239.59.nnn.
tedsterJust found my notes. The IP where PR will not be updated is indeed 64.233.183.104 - as UK_Web_Guy said.
Matt has been kind to elaborate more about that DCs. When asked about the reason why 64.233.183.104 wouldn’t update its PR. He replied [mattcutts.com] :
..... the short answer is that there aren’t enough machine resources at that particular data center to switch over the infrastructure until a few months from now (data centers can get full). I’d just ignore that data center; it’s serving older data.
[edited by: tedster at 12:24 am (utc) on Nov. 23, 2006]
I wonder why that one datacentre is affected and not the others:
gfe-nf.google.com - 64.233.183.x - x104 x99 x147 x103
It isn't one of the oldest datacentre names, but it is one of the very few that has four GFE aliases set up.
Did Matt ever confirm that it was just 64.233.183.104 or was it 64.233.183.anything here?
[Tedster, you've been tagged]
Just to mention that it has been a roll-back today for several hours followed by "turbolance" on most DCs.
Every year when we approach the X-Mas shopping, those Googlers start their traditional X-Mas-Tinkering :-)
I'm seeing quite a bit of the jostling right now. Two sites that were older but started ranking this past summer have blipped back out (still indexed just fine, simply no longer ranking). The "" and &filter=0 tricks aren't bringing them back into the first 1000 results, so something is definitely going on at the plex.
What is particularly interesting is that on one of the sites, it actually improved on the allinanchor: results for the phrase in question -- I wish I had recorded the number of total results before the weekend and the number of results now, but it almost feels like an incomplete data push.
Cygnus
[Edit reason: found more data to include]
[edited by: JoeSinkwitz at 6:41 pm (utc) on Nov. 25, 2006]
I hold no illusions that any of the operators report as accurately as they once did, but "allinanchor" seems to do something still regarding inbound linking, and from what I can tell, a mashup between allinanchor / allintitle / allintext is pretty close to serps I see on a day-to-day basis. Thus, I still check, just to see. In some cases it can still provide a glimse into the future of serps to be...and of course it can also provide a painful tease that never materializes.
Anyhow, this morning the allinanchor and allintitle improved, but the allintext dropped out of the top 1000, which seems to have corresponded to some of the massive movement I've been seeing.
I don't want to hijack the thread with my own issues, but it seems to be on all the named datacenters -- for those that come back from a long weekend and see some missing results, check your allintext; if you are AWOL there, then we might be able to build a commonality. In the event our friendly moving target that is KW density changed, I added a paragraph of mostly useful text to dilute the usage of my key phrase -- by this time next week I hope to see if I had triggered some errant filter there.
Cygnus
I am seeing G loving scrapers more than the original content holders, but that's another issue altogether.
Cygnus
You migt be able to see the diference in number of backlinks if you compare for example the folowing two DCs:
[216.239.59.107...]
and
[66.102.9.107...]
Haven't caught the higher BL totals but i've seen large SERP's movement on these DC's
ht*p://216.239.39.*
Vimes.
[edited by: Vimes at 10:37 am (utc) on Dec. 21, 2006]
In fact I see right now large movements on most of the DCs. That must have started during the last hour or so (my local time now 12.12 pm, GMT +1).
May be its the start of the monthly Matt Cutts Data Push :-)
How come you youngsters with fresh eyes and strong visions can't see what I see with my old reseller eyes. May be its only "european backlinks update" :-)
ok seeing it now,
All over the Dc's now like a rash :)
64.233.167.*
64.233.183.*
66.102.9.*
72.14.203.*
Hmm not seeing the SERP's that first caught my attention on these Dc's tho they seem to have been push from sight for at least a while.
Vimes.
There are 3 sets of link infomation floating around, two of the sets are well populated across the Dc's there is however another set that only seems to be on a single dc's at any one time, can't give you the Dc address as every time i come across it, it moves on before i can research it.
are you seeing that set as well?
Vimes.
[edited by: Vimes at 1:25 pm (utc) on Dec. 21, 2006]
Yes.. I see the two sets.
Maybe you can see the third set (old results) here (But things are changing very fast).
64.233.167.99
One of my sites european has increased it's pages by 500%, while yesterday 90% of pages were gone.
It seems our kind WebmasterWorld fellow members Matt Cutts & Adam Lasnik are distributing X-Mas gifts among the rest of WebmasterWorld members today. Keep those increased numbers of indexed pages coming..please :-)
[edited by: tedster at 6:41 am (utc) on Dec. 22, 2006]
[edit reason] member request [/edit]
Might be time to go out and mow the grass...
What is the Matt Cutts Data Push?
Called after our kind WebmasterWorld fellow member Matt Cutts. He is also the Head of Google WebSpam Team.
Here is what Matt wrote [mattcutts.com] about "Data Push" and "Data Refresh"
Matt Cutts:
.... A data push is a superset of a data refresh (that is, a data refresh is an instance of a data push). Typically a data refresh is something with a well-established history, e.g. we have automatic tests in place and the data to be sent out is sent out automatically (assuming that all the automatic sanity checks pass). A data push may tend to be less automated and thus may undergo more evaluation. But the terms are often used interchangeably by Googlers, because we know what we mean, so you’re pressing for a pretty fine connotation.
Sometime during 2006 we have noticed that those Data Push / Data Refresh happen around once a month. Of course not sure that its going to stay that way.
Its worth to mention that also during 2006, a "Bad Data Push" happened and it was announced by our kind fellow member Adam Lasnik (member of Google WebSpam Team).
Late night Google Datacenters Watching ;-)
I see at the moment the following sets of DCs having their own serps which might differ from the rest of DCs.
64.233.167.99
64.233.167.104
72.14.203.99
72.14.203.104
72.14.207.99
72.14.207.104
Very exciting indeed!
Do you see changes (plus or minus) in number of your backlinks on these DCs?
[66.102.7.104...]
[66.102.9.99...]
[66.102.11.99...]
[216.239.63.104...]
[216.239.53.99...]
[216.239.59.99...]
[216.239.59.104...]
[216.239.57.99...]
[216.239.57.104...]
