Earlier quoted context omitted.
I did see the Fail Whale once or twice last week and my client (TweetDeck) occasionally hits API errors, so it isn't perfected quite yet. But handling 1800 tweets a second and pushing them to real-time streams is no small task.
handling 1800 tweets a second [...] is no small task It's funny how people consistently overestimate that. Actually, yes, it is a fairly trivial task and there's no justification for failwhaling over it when you have money to buy competent developers. Many companies process orders of magnitudes more than that, under much harder constraints and much more complex requirements (think financial industry and telecoms).
Phone companies and financial institutions don't typically have messages which affect millions of accounts, for a start.