Blackberry reveals failure cause
The maker of the Blackberry wireless e-mail device says an insufficiently tested software upgrade was the cause of this week's network failure. — Blackberry's US and North American users lost their service on Tuesday and Wednesday as a result of the problem.
Context & Ripple Effects
Two days after Research In Motion restored service following the Tuesday–Wednesday blackout across its US and North American user base (service was back by April 18), the company has named a cause: a software upgrade it now admits was insufficiently tested before deployment. The New York Times picked up the disclosure alongside the BBC, giving the explanation wide circulation.
That framing matters because BlackBerry's appeal to its core base — enterprise IT departments running always-on wireless email — rests precisely on reliability, and the admission converts a technical incident into a credibility question about how RIM validates changes to its network.
First-order effects
- Enterprise customers who route corporate email through BlackBerry's infrastructure get a rare public admission from RIM that a change reached production without adequate testing, forcing IT buyers to question the change-management discipline behind the service.
- RIM must spend immediate goodwill explaining the failure to carriers and corporate account holders whose messaging went dark for two business days.
Second-order effects
- Rivals selling alternative push-email setups — Microsoft-based Exchange mobility stacks and device makers courting the same corporate accounts — gain a concrete talking point against BlackBerry's reliability pitch in renewal negotiations.
- Large enterprise buyers are likely to press RIM and carriers for stronger service-level commitments or contingency plans before renewing fleet-wide BlackBerry contracts.
Third-order effects
- If untested upgrades recur as an outage cause, RIM's centralized network design — every message flowing through infrastructure the company controls — shifts from a selling point (security, manageability) to a visible single point of failure that competitors can attack.
- Repeated reliability incidents would push enterprise mobility purchasing toward vendors and architectures that treat uptime guarantees, not features, as the primary selection criterion.
The trend: As mobile email becomes mission-critical corporate plumbing, carrier-grade change management and published reliability records are becoming a competitive axis in enterprise mobility, not an assumed baseline.