Jaiku, the microblogging service I use, has been frustratingly often down in the last couple of days, apparently kicking off another mass migration towards Twitter and Brightkite.
And they report it only in human-readable way, not in fashion a browser, a proxy or a search engine would understand it. While being down, Jaiku still responds with HTTP 200 OK:
HTTP 503 Service unavailable would be much nicer. For instance, that is what Midgard produces if the database goes down.
Technorati Tags: brightkite, jaiku, http, twitter
