Datacenter Watch: 2006-06-21

[angiolo]

< continued from [webmasterworld.com...] >

With reference to:

64.233.187.99 Copra
64.233.163.100 Copra Variant
64.233.185.107 Original Turd
66.102.9.99 Turd Variant

I get the same results on the first three.
Different on Turd variant

Do you think that Copra will propagate to all Google datacenters?

[edited by: tedster at 9:36 pm (utc) on June 21, 2006]

[petehall]

It's wierd... Copra is everywhere and yet hardly ever used!

[jonathannelson]

It's wierd... Copra is everywhere and yet hardly ever used!

its because Google has disabled several features that launched with the BigDaddy update (canonical fixes, new caching proxy, site: feature, www vs. non www, etc), if not the entire infrastructure itself. check your logs. if your logs (visitors, traffic, sessions, etc) are emulating that of the days right before February 14, 2006. chances are, you are a victim of Google's recent index deprecation. think of the canonical issues that were addresed with the BG update. are you still seeing these in your own KW serps? think of how Google uses its new caching proxy. start playing devils advocate. start constrast/comparing pre & post BigDaddy and measure it against your own site(s).

JN

[petehall]

Hi Jon,

I did not word my comment well enough.

I meant I hardly ever see Copra results on Google.co.uk, yet they are apparently the dominant set of results.

:-)

[sandpetra]

same here - it seems to have gotten so far and then......stopped.

Although i did test it on some other computers - why are their default google dcs showing copra and mine isnt?

[petehall]

Mine is on and off, but mostly off.

It's starting to bug me.

This is AltaVista territory now...!

Please: one or the other!

[Hissingsid]

I'm seeing Copra on .co.uk 216.239.59.104 but my traffic is a disaster today. I wonder what other folks in the UK are seeing.

There is strong evidence that although Turd and son of Turd are very much the minority that this is not the case for the UK. Half of the DCs that have been seen serving .co.uk are Turd (or son of Turd) and half are Copra. Therefore in the UK we have a much higher chance of seeing Turd than the rest of the World.

Sid

[sandpetra]

well teh site:command is duffed on 66.102.9.104 - showing 10 x the amount of pages I have got in the site. Just when it had recovered!

[garyr_h]

Any predictions when Copra will be pushed into the other DCs?

[jrs_66]

Has anyone started to think that maybe the DC's will NEVER be in synch again... those days appear to me to be over. Big daddy has changed the way Google operates, get use to it!

[Instigator]

Hissingsid.. I've been seeing Turd, 66.249.93.104 all day here in London, and I believe most people in this region are seeing 66.249.93.104, meaning very poor traffic for my site which is London orientated.

[CainIV]

I'm seeing Copra on .co.uk 216.239.59.104 but my traffic is a disaster today. I wonder what other folks in the UK are seeing.

Ditto. Traffic boomed yesterday only to slump today. Results for me are not showing copra here anymore...

[Tigrou]

There was talk here in week(s) past that we should create some sort of update to the <DC Checker Tool> with the 90% of DCs that it doesn't capture, or at least do a representative sample. But that assumes that each DC is equally used. And it's patently obvious here that this isn't the case -- at least with the 50 normally used.

The "market share" of each DC (and therefore algo/variant) could be determined though an update to <DC Checker Tool> but that's a lot of work and is it worth it even to the most ardent DC watcher? If not how accurate is DC Watching...I mean it's kinda fun to see you're number 1 in good results across 50% of tracked DCs but disappointed that's not reality in live results.

Thoughts?

[edited by: Tigrou at 8:16 pm (utc) on June 27, 2006]

[avalanche101]

Okay,
I'm seeing changes in our sector, our site seems to be back to where it was before big daddy.
Anyone else seeing changes?

[b2net]

Yes I see changes, quite big actually because I have lost some new sites. Wasn't BigDaddy supposed to make future changes only minor? This is stressful.

[toothake]

"Anyone else seeing changes?2
LOL my site was fixed now back to 3 months ago all supls ech...,well just LOL.

[toothake]

and if you ask me why I LMFAO is because the whole thing is becoming a soap opera with a cheap scenario (worst then The Bold and the Beautiful)

[Wibfision]

Seeing huge changes to traffic to my site, started this evening at around 8:00 pm GMT. So huge I would call this an update. Is anyone else seeing this?

[skweb]

Me too. For one of our big/old websites I am seeing major drop in traffic and some really weird results. If this is the future of Google then I am doomed; but it seems like an update to me.

[Phil_AM]

My site is back to pre BD.

Thank the lord.

Also, this pre BD set is on 90% of the <online tool's> posted DC's.

[edited by: tedster at 2:49 pm (utc) on June 28, 2006]

[b2net]

I'm afraid these results will stick unlike May 16 test results. It's move-your-site-to-another-url week.

[Tinus]

I just checked my sites. One site traffic just doubled. Other site has five (!) times as much traffic. Everything started 2,5 hours ago. Before that traffic was a kind of normal. Third site traffic is the same as usual.
So big changes are going on. My sites are all travel related and we lost soccer but I don't think both facts explain these sudden changes.

At may 16 traffic also went up with the same two sites and that lasted for two days. It wasn't this extreme though. Happened to more people then. Might be a glitch.

[dazzlindonna]

My site that got destroyed in the Dec. 27 "data refresh" is now back. We'll see if this lasts for more than a day or two.

[Phil_AM]

Well, the good thing that happened here is that the site: command actually shows my index page first for the first time since BD cannonical issues set in.

However this result set is NOT pre BD like a I thought, as there are many new players on the top 3 pages for the kw's I monitor.

My hunch is an entirely new update, but unlike the last month's worth of stuff, this hit quick and updated on 90% of the dc's <used by an online tool> within 4 - 6 hours. thus an update and not G testing results or tweaking anything.

For sites like min that were hit with a cannonical issue back at BD, this is a welcomed event!

[edited by: tedster at 2:50 pm (utc) on June 28, 2006]

[jrs_66]

This thread is beginning to sound like a doomsday cult's monday meeting... 'the big one is coming! run for your lives!' oops... maybe next week.

[teomax]

i just came here to see whats going on, because the results in my area has dramatically change -> probably one of the worst results on google i have seen in 4 years of my webmaster career.
probably they are testing some new filters or what...

[kidder]

Yesterday a check of the data centers for our site shows us good results on some but mixed results on others - using the site: command our index page is burried behind internal pages. Today the same check shows us the "mixed data" from the site: command seems to be spreading through the other data centers. Our page count is sky high jumping from 600 pages to over 22,000 overnight - and all mixed up? It's all guess work boys and girls. If google does not know then how are we supposed to know?

[avalanche101]

Okay,
so everyone who's reporting site going back to pre BD, did your site also recover on may 16th?

[MissusC]

Okay, so everyone who's reporting site going back to pre BD, did your site also recover on may 16th?

YES

[steve22]

hi
i still see old results @ 64.233.189.104
my site completely disappeared everywhere else :-(

[kidder]

This is the same but different... One of our other sites we thought was immune has also been hit this time around. The pages are still in the index just the way they are being reported and served is the change. If you run the site: command and then space "keyword" google serves up supp pages before the relative data..