Commentary

Good Thing RIM Doesn't Have A Campy Slogan About Reliability. Otherwise I'd Be Skewering It Right Now

Is anyone else getting tired of BlackBerry e-mail slowdowns and outages? I am, and I don't even use a BlackBerry any more. IT admins fielding cranky phone calls from e-mail-deprived workers must really be getting tired of it. Reports were flooding user forums this morning of yet another failure in RIM's e-mail service. If your enterprise BlackBerrys are kaput, what's your back-up plan?

Is anyone else getting tired of BlackBerry e-mail slowdowns and outages? I am, and I don't even use a BlackBerry any more. IT admins fielding cranky phone calls from e-mail-deprived workers must really be getting tired of it. Reports were flooding user forums this morning of yet another failure in RIM's e-mail service. If your enterprise BlackBerrys are kaput, what's your back-up plan?I remember the first time my BlackBerry stopped receiving e-mail about 2 years ago. I reset the device, performed an enterprise activation, and then bagged it and called IT. When I got through, my then-IT admin told me that he'd already received other calls. His exact words were, "It's bigger than just you, Z." It was the better part of a day before e-mail was restored. Was it a big deal at the time? Nope.

Last April, when e-mail went down across much of the company, it was a much bigger deal. I was on deadline for several stories and needed to communicate with a couple of editors. It bungled things up. Not the end of the universe, but I am not a salesperson. Or an executive. Nor did I have only 45 minutes between flights to catch up on office communications, as some likely did.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

When enterprises put trust in technology, they are obviously taking risks that the technology might one day fail them. Every company experiences downed servers, or electrical outages, or whatever. It's going to happen.

But communication -- especially via e-mail -- is vital for many organizations. When companies put the success or failure of their business in the hands of a company such as RIM, they need to trust that service. In the grand scheme of things, the loss of mobile e-mail for, what, a total of maybe 24 hours so far this year, shouldn't kill any business. But one day an outage might. You just never know. What is your enterprise's back-up plan?

Consider this. Most of you probably know that I use Google apps and services for the bulk of my productivity tools. Gmail is chief among them. So far, uptime has been 100%. I have never not been able to retrieve my Gmail from the Internet or a mobile device of any type. Mobile Gmail always works. And it's free. So is the client on my device.

So far, I haven't seen anything beat it. Does it support all the crazy enterprise functions that many businesses need? Well, not all of them, but it's getting better.

RIM hasn't publicly acknowledged this outage, and hasn't quelled any fears that e-mail addicts have about the reliability of its service. RIM, time to come forward and offer more than "it was a system upgrade" type statements. Your faithful have been shaken. How do you plan to hold on to your enterprise e-mail empire if you can't keep your services running consistently?

Inquiring minds want to know.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links