Executive summary: if you want to play with a Bigdaddy data center, hit 22.214.171.124 instead of 126.96.36.199.
Longer explanation: I spent this morning writing posts about url canonicalization, inurl:, and 302 redirects so that everyone would be well-versed to evaluate Bigdaddy. In the post about 302 redirects, I even mentioned a search [sf giants] that Bigdaddy does better on than the current Google system. Then I got this comment by Michael Weir:
fascinating post – thx Matt! Although, at the time I post this bigdaddy was returing www.sfgiants.com as #1 when querying “sf giants”. I don’t think bigdaddy likes you. 🙂
I think my mental thought was “Huh. That’s not good.” I walked down and talked to the Bigdaddy folks, and sure enough: 188.8.131.52 has been taken down for testing. Note that if you go to 184.108.40.206, you’ll still get a Google search box–it will just be regular Google, not Bigdaddy.
So it looks like 220.127.116.11 is the best IP address to use when testing Bigdaddy. That data center should be showing Bigdaddy results more reliably. Also, it looks like [sf giants] is a fine query to see if you’re hitting Bigdaddy. 🙂 If you get giants.mlb.com at #1, you’re searching Bigdaddy. If you get www.sfgiants.com at #1 and an uncrawled url http://sanfrancisco.giants.mlb.com/NASApp/mlb/sf/homepage/sf_homepage.jsp at #3, you’re hitting the older Google infrastructure.