One of my pet peeves is currently when Twitter Search is down - there goes being able to zone into conversations on any given topic from bsdisms, following cloud computing, etc.

Tired of seeing:

Status: 500 Internal Server Error Content-Type: text/html 500 Internal Server Error

How difficult is it to fix something that was not broken when it was Summize?

This is what a reply from twitter looks like:

HTTP/1.1 200 OK
Date: Wed, 04 Mar 2009 20:52:44 GMT
Server: hi
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=300
Expires: Wed, 04 Mar 2009 20:57:44 GMT
Vary: Accept-Encoding
X-Varnish: 1089043412
Age: 0
X-Cache-Svr: searchweb008.twitter.com
X-Cache: MISS
Via: 1.1 varnish, 1.1 bc1-rba
Content-Length: 122
Connection: Keep-Alive
Set-Cookie: _search_twitter_sess=*snipped*; path=/

Status: 500 Internal Server Error

Content-Type: text/html

500 Internal Server Error

UPDATE:

Okay it's up if I go via reverse proxy in the USA - so it's just down for South Africans.

UPDATE:

IS have added some rules to their netcaches and search.twitter.com is working again.