Update Saga. Part 5

[Brett_Tabke]

What say you?

Over and done with?

All done all through?

[Brett_Tabke]

This topic has gone a bit off course here.
Lets pause for 24 hrs and see what it looks like tomorrow.

[lee_sufc]

Just noticed the "good" results from the other day showing up on a couple of DCs (including [64.233.167.104)...]

Anyone else noticing this?

[reseller]

If what I see on the 4 following DCs is still Jagger3, then nothing new under the sun yet ;-)

66.102.9.99/104
66.102.11.99/104

[lee_sufc]

reseller - what do you think of [64.233.167.104...]

[reseller]

ee_sufc

>>reseller - what do you think of [64.233.167.104<<...]

I like what I see :-)

Looks like a Jagger3 serps for the sector I'm watching.

[lee_sufc]

this is what I was hoping the other day....before they all dissappeared.

this time...i am not keeping my hopes up!

[reseller]

Maybe something will happen tomorrow Monday when the folks at the plex start working again. Hopefully J3 will migrate giving most of us the chance to go on with our lives and start contributing to other very interesting threads like this one :-)

[webmasterworld.com...]

[steveb]

64.233.167.104

Yes the mildly healed results have poped back there. Jagger3 based, but quite a lot of awol sites reappearing and/or ranking normally. Still not a full-blooded fix, but better than the incomplete Jagger3 results.

[phpdude]

64.233.167.104

I think those results stink.

Seems everybody has a opinion as to what is fixed or not.

The results showing in that IP are far from fixed in the area I'm interested in.

It appears that whatever they are doing is affecting different industries at different levels.

[petehall]

I like both 64.233.167.104 and 66.102.9.104.

Just wish we could move on from this update now to be honest.

Join me in my quest for the next non-update.