Quite a few of you saw my post from last night about Twitter’s failure. Quite a few of you have noticed that it’s still going on. We’re about to enter day 3 of Twitter FAIL and still aren’t getting a whole lot from Twitter about it.

Yes, Twitter did in fact acknowledge the issue yesterday in the GetSatisfaction forum. But one problem with this is that most Twitter users have no idea there is a GetSatisfaction forum. Would it not be a good idea post about that on the Twitter blog – if not post about the problem itself? Or even better, how about one of those little yellow boxes you now love to use on the main site to alert us to the issue?

And yes, Twitter does have a twitter_status account to update on downtime. The problem? Neither this nor the GetSatisfaction info have been updated for over a day. (Also, is anyone even seeing the twitter_status updates in their stream?…)

The real problem here is that it’s not clear there is any problem. It’s not like the site is down. It’s just not working correctly. You shouldn’t just leave a broken site up with no explanation that it’s broken.

As The Last Podcast says, talk to us when things go bad. This is a communications breakdown.

PASS: I pointed out something that went wrong with FriendFeed once on FriendFeed – not only did they fix in within minutes, they actually acknowledged my note and told everyone what the issues was.

FAIL: What Twitter is doing.

If this problem spills over into tomorrow – or worse, Tuesday when the huge Web 2.0 Expo starts in San Francisco, expect a world of pain for Twitter. If they would simply acknowledge and update the users it might not be so bad. Otherwise we’re going to see Bitchmeme taken to a whole new level.

Follow my updates on Twitter here. Not that you’ll see said updates until they, you know, fix Twitter.