Commentary

Stephen Wellman
 

BlackBerry Mobile E-Mail Crashes Across The Entire Western Hemisphere

BlackBerry users this morning woke up to find that their precious push e-mail service was down. Push e-mail junkies across the entire Western Hemisphere were without their fix. Will this outage be the break BlackBerry's competitors have been looking for?

BlackBerry users this morning woke up to find that their precious push e-mail service was down. Push e-mail junkies across the entire Western Hemisphere were without their fix. Will this outage be the break BlackBerry's competitors have been looking for?Obviously, this is a huge deal. While Research In Motion encouraged users to make backups, that's just not enough in this era of instant competition. This outage has impacted thousands of businesses in a major way. Push e-mail for many managers and employees is mission critical, and when a mission-critical app goes down, business suffers and IT managers get pressure to look at new solutions.

RIM has been adding new subscribers to its BlackBerry service at a faster-than-normal rate in recent months. This rapid expansion may have contributed to the crash. RIM had better move fast to take care of this and to make sure it doesn't happen again. If BlackBerry has any competitive advantage against the likes of Nokia, et al, it's the service's sterling reputation as a bulletproof system that just works. Outages like this tarnish the BlackBerry brand and open new opportunities for RIM's competition.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

If I were Nokia, Motorola, or Microsoft, I'd be marketing the heck out of this BlackBerry outage. Now, can any of RIM's competitors actually capitalize on this?


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