Blackberry Internet Mail service seems to have borked this morning, leaving millions of Crackberry addicts without an excuse to avoid their children. I'm sure in the end it will have been some silly admin error that caused it, but as we grow more and more used to (and addicted) the gigantic signaling fabric that the Internet has become, it is going to be harder and harder to cope with these kind of outages. Why just last week, we were just getting over the Skype outage during which I heard podcasters claim they were going to be "put out of business" by bad Skype capacity planning.
What is especially rough about the Blackberry outage is that it is endemic of the types of outages we can expect to see if we continue switching to proprietary (and thus centralized) messaging platforms. For instance, all sorts of web services have sprung up to replace email with varying degrees of success. On some sites, the internal messaging is peripheral to the experience (Flickr), but on others, it is either central (Facebook), or the experience (Twitter). Unfortunately, these systems were designed as centralized web services. And even well implemented web services can go down, mostly because the redundancy is added after the initial design. For instance, I'm sure that Facebook's database layer is sharded and replicated, its assets are on multiple CDNs, and its application servers are geographically distributed— but because the application was never designed to be distributed, these solutions will only take robustness thus far (especially after you add in the potential for human error at each of these layers).
Contrast this to decades-old email, or rather email + DNS. The combination of a very simple protocol for message exchange (SMTP) with a very flexible address resolution system (MX records in DNS) means that is is pretty hard to make all of email "go down." Sure the big centralized services like Gmail and Hotmail can have outages, but all of those law firms running Exchange, schools running Sendmail, and startups running Postfix will keep right on chugging. And even when these small poorly managed mail servers fail, there is usually some marginally better server at the ISP queueing up email just for the occasion.
Ray Tomlinson and his colleagues at BBN deserve a ton of credit for having put together a system in the 1970s that could grow to the scale and scope that it has while remaining more robust than a lot of what has come after. All of the rest of us should take a page out of their book in working towards improving the fabric of the Internet.