| 11:49 pm on Nov 15, 2009 (gmt 0)|
For me 126.96.36.199 is very similar to the sandbox in the early stages.
| 5:58 am on Nov 16, 2009 (gmt 0)|
I find these results do not shift me to local settings if I search using this format - [188.8.131.52...]
| 2:29 pm on Nov 16, 2009 (gmt 0)|
Not seeingf any difference on that datacentre, but am seeing what looks like caffeine did last time I looked at it, which was about 1 month ago, on 184.108.40.206
anyone seeing anything caffeine like on 220.127.116.11 ?
| 2:52 pm on Nov 16, 2009 (gmt 0)|
When I search on google.com in the UK the IP is 18.104.22.168
| 2:59 pm on Nov 16, 2009 (gmt 0)|
Are you seeing anything different Sid?
| 3:15 pm on Nov 16, 2009 (gmt 0)|
It has changed again now. When I go to 22.214.171.124 for example via my browser URL box I go to a page with a Google English logo on it. When I then search it redirects me to 126.96.36.199 for the SERP.
| 4:14 pm on Nov 16, 2009 (gmt 0)|
Someone else has just posted on DP forum that they see Caffeine is on 188.8.131.52
You heard it here first, come on Matt, pop in for a comment, it'll be like the google dance days with GoogleGuy!
| 6:01 pm on Nov 16, 2009 (gmt 0)|
|Caffeine is on 184.108.40.206 |
Yep, it's on all the 66.102.7.XX
It IS flickering on and off so those who don't see it may be need to check at different times.
| 6:12 pm on Nov 16, 2009 (gmt 0)|
i don't think this is caffeine..
anyone else does?
| 6:35 pm on Nov 16, 2009 (gmt 0)|
As I recall, watching a Matt Cutts video of Pub Con the other day he did say the data center showing Caffeine results would be switching on and off. It had something to do with us webmasters overloading that server. Ha!
| 6:38 pm on Nov 16, 2009 (gmt 0)|
Matt Cutts tweeted this is NOT Caffeine:
| 6:42 pm on Nov 16, 2009 (gmt 0)|
yep... definitely something happening on 220.127.116.11, but not Caffeine as I remember it from last week (or whenever they took it down).
| 6:45 pm on Nov 16, 2009 (gmt 0)|
if you look at [twitter.com...] you can see matt is responding to the asertion caffeine was on 18.104.22.168
22.214.171.124 is the caffeine i've seen
| 6:46 pm on Nov 16, 2009 (gmt 0)|
|Matt Cutts tweeted this is NOT Caffeine: |
That answer was reffering to 126.96.36.199
| 6:47 pm on Nov 16, 2009 (gmt 0)|
Matt Cutts tweeted this is NOT Caffeine:
lol you'd be amazed at how un-knowledgeable he is about the actual rollouts. (documented several times on this forum...and it's not his department)
He was vague, "don't believe".
If it TRULY isn't the sandbox datasets,
which is what it looks like,
AND it certainly isn't the current datasets.
it's the "holiday datasets"...
Which would roll out rather quickly considering they would need to push those almost immediately.
Let the FUD commence. ;)
| 6:51 pm on Nov 16, 2009 (gmt 0)|
no.. i guess it refers to 188.8.131.52
"Update #1: Some are saying this data center has moved to 184.108.40.206."
| 6:53 pm on Nov 16, 2009 (gmt 0)|
I think some of the confusion between us on here is that this is moving in and out of this DC 220.127.116.11
It has been reported it will show off and on, IMO i have definitiely been looking at caffeine on 18.104.22.168 , but it ain't that different to normal old google anyway!
| 6:56 pm on Nov 16, 2009 (gmt 0)|
PS, I'd expect this to flip in & out as google try to prevent excessive load on these IP's after all if they wanted us hammering it, they would have left the ww2 site live
| 7:26 pm on Nov 16, 2009 (gmt 0)|
That's exactly it. At Pubcon Matt explained that the server team thought he was mad to even suggest using one stable IP for Caffeine before it rolls out fully. Their entire load-balancing structure is not set up that way, and they didn't want to "punch a hole" in the load-balancing IP assignments.
So he will continue to campaign for some accommodation for websmasters, but it's most likely going to a "best bet" rather than a sure thing.
| 7:37 pm on Nov 16, 2009 (gmt 0)|
Sorry about that. Thank you for correcting me.
| 9:38 pm on Nov 16, 2009 (gmt 0)|
I'm 100% sure I saw the google caffeine results live last night for a couple of hours -- i was searching through a proxy server. The reason I noticed is that my entire site was back in the serps stronger than before. Looks like things are in motion. The quicker the better on my end.
| 4:36 pm on Nov 21, 2009 (gmt 0)|
Just wanted to say that I have been watching this and testing caffeine since the anouncement months back. At this point I can say with some confidense that what I saw prior to a few weeks back was indeed caffeine results in the normal search. It appears since shortly after the beggining of November Google pulled Caffeine back and is testing it randomly on a few data centers. So I agree with the conclusion that Caffeine was implemented and being served for well over a month previously as stated by others on this board at the time.
Just wanted to give my 2 cents. Currently I am seeing caffeine randomly after reloading a few times on [22.214.171.124...]
| 5:25 pm on Nov 21, 2009 (gmt 0)|
For someone who is late to the Caffein watch is there some stand out feature that would let you know which results are Caffein?
| 5:45 pm on Nov 21, 2009 (gmt 0)|
What I have noticed is a subsatntial difference in the number of pages returned, Faster results and to me much more rellevant.
| 7:21 pm on Nov 22, 2009 (gmt 0)|
Trying to come to a deeper understanding of Caffeine, I recently reviewed this thread and its external links: The Google Search Query - a technical look [webmasterworld.com]. What struck me about it was this quote: "Today it's estimated that [a single Google query] travels across 700-1000 machines, a figure that has nearly doubled since 2006 perhaps due in part to the introduction of Google Universal."
Then the Google PDF document goes further:
|the strategy is to partition the processing of all documents by |
• randomly distributing documents into smaller shards
• having multiple server replicas responsible for handling each shard, and
• routing requests through a load balancer.
It seems to me that Caffeine is an intervention into the complexity of that process - and hopefully one that simplifies all those potential spots for data errors. I'm looking forward to the full roll-out.
| 5:40 pm on Nov 24, 2009 (gmt 0)|
A quick question regarding testing caffeine results for UK based queries. We only supply UK based clients and our site has always rated well on Google.co.uk. When testing Caffeine results I only ever found US results and without adding 'UK' before our valued search terms, which does not give an exact report compared to local results, I was wondering if anyone knows of a filter that would allow us to test the results for caffeine.co.uk results.
| 8:45 pm on Nov 24, 2009 (gmt 0)|
|allow us to test the results for caffeine.co.uk results |
Unless anyone knows better I think the best you can hope for is to compare Caffeine (if you can find the real thing) to google.com results and hope that the UK filter, when it is applied to Caffein has a similar effect to what is currently happening. In other words you want google.com and Caffeine results to be the same and then hope that some cleaver fellow in Googleplex doesn't decide to monkey with the UK filter between now and when Caffeine rolls out in the new year.
| 8:48 pm on Nov 24, 2009 (gmt 0)|
To test UK results on a domain other than google.co.uk you can add the parameter below to the result URL:
| 12:36 am on Nov 29, 2009 (gmt 0)|
I don't know if anyone has seen this yet but Matt Cutts has confirmed that 126.96.36.199 is pointing to the Caffeine data center atleast 50% of the time.
Talk about this is found over at SEO Round table [seroundtable.com].
[edited by: Robert_Charlton at 1:16 am (utc) on Nov. 29, 2009]
[edit reason] added link to SER [/edit]
| 1:31 am on Nov 29, 2009 (gmt 0)|
From Matt Cutts' comments....
|...I think it's really risky to take a few threads and turn that into a "major Google update." |
.... So 188.8.131.52 does hit the Caffeine data center more often than other IP addresses, but it's always been the plan that Caffeine would roll out at one data center (no more data centers will get Caffeine until at least January)....
But I would avoid generalizing.... on a lot of the webmaster forums you can't tell what site they're talking about, so it's hard to do any debugging on what might have happened to individual sites there.
| 2:22 pm on Dec 4, 2009 (gmt 0)|
To go back to Elixir's post on 24th Nov:
"It was nice of Matt to stop by and put our minds at ease but where is the explanation for the bizzare results especially in the travel sector. I also saw one result today where 6 of the top 10 results were differnet blog posts from the same blog as indents. The blog did not even belong to the person I was searchin for."
I am finding some very funny rankings in the travel sector this month. Does anyone know why this industry might be affected particularly by caffeine, and is this something that all travel sector SEO's are finding?
| This 238 message thread spans 8 pages: < < 238 ( 1 2 3 4 5 6  8 ) > > |