CNBC and Engadget Mobile have a story about the Blackberry service being down again. Now there is even a website dedicated to alerting users of problems http://www.dataoutages.com/ .
Now, the problem is not that it goes down or for how long it goes down - no system has 100% uptime. The problem is best quoted from the CNBC article "RIM was not immediately available for comment and its e-mail gave no estimate on when service may be restored or how many individuals could be affected"
In other words, if you are responsible for the messaging infrastructure for your company and the President's BlackBerry stops working, he will call you and what are you supposed to say? "....I don't know what the problem is, how severe it is, or how it will be fixed because it is completely out of my control and RIM won't even comment on it". This is one of the key reasons why companies are migrating their BES infrastructure to Windows Mobile: control.
Here is a list of what I personally think are a the critical challenges with RIM's architecture:
These I think are the reasons why I have yet to meet an IT manager, director or CIO who after learning about WIndows Mobile tells me "You know, we are pretty happy with BlackBerry and we plan to continue using them as our wireless platform for the future".
As a reminder, all posts on this bnlog represent my personal opinion which may not be the same of my employer. Your comments are welcome as always.