70 Million Blackberry Subscribers Have Crashed

BlackBerry services across Europe, the Middle East and Africa have crashed, causing widespread disruption across the continents.  The glitch began disrupting services from 11am (GMT) after a service failed in one of Research in Motion’s datacenters in Slough, near London.

Users have been unable to browse the web, send or receive email messages across personal accounts, or use the popular BlackBerry Messenger instant messaging service. It is thought that at least 70 million subscribers around the world are BlackBerry customers, with as many as 50 percent of that in the European region affected.

A few hours after Blackberry maker RIM said all services were “operating normally” users have complained of a new crash.  Twitter is full of angry users reporting renewed issues with their handsets and an inability to send messages and email. The problems now seem to have spread to Latin America as well.

BBC News – Blackberry users complain on Twitter of fresh crash

Messages on Facebook – from Blackberry user Mo’Tlatsi Diale in South Africa said:

Merry Christmas and Happy New Year in advance buddies, just incase Blackberry internet services aren’t sorted out in time……*all my love*

Stan Wilde from Tamworth in Staffordshire on Facebook said:

AGAIN! Major Fail BB, sort it or lose customers!

The outage, which began at 11am on Monday, was resolved some 20 hours later, with the exact cause still unknown. However, the Guardian reports that RIM has been ignoring server problems for many years.  A former RIM employee told the newspaper that the company’s server architecture was not a priority, and instead they chose to focus on growth.
They have their own clunky infrastructure to do something that you don’t really need a clunky infrastructure to do anymore,’ the source continued.

iPhone developer Apple announced that it would be releasing its new iOS 5 operating platform for existing users on Wednesday (October 12th), two days before its new iPhone 4S goes on sale.

 

 

%d bloggers like this: