2 min read

As fix begins, worldwide BlackBerry users still have problems

Service slowdown reaches North America for first time

BlackBerry users Wednesday reported that problems are continuing into a third day in Europe and Asia, after Research in Motion reported on Tuesday that a fix was underway.

And for the first time, BlackBerry service slowed in North America today, according to a tweet from 680 News in Toronto shortly after 7 a.m. EDT. Others in North America tweeted BlackBerry Messenger service was down.

Elsewhere, Vodafone Qatar told the Wall Street Journal on Wednesday that every one of its wireless subscribers was affected to some degree by the service slowdown. Some, it added, had difficulty sending email or instant messages.

Sister publication Computerworld reported on Wednesday mid-day (7 a.m. ET) that users in the UK and Europe saw service resumed briefly Wednesday morning after a 17-hour outage on Tuesday, only to crash again at 9:30 a.m.local time (4:30 a.m. ET).

Computerworld said Twitter users in the UK resorted to using PCs to tweet concerns, with several noting the public relations problem facing RIM.

On Tuesday, delays in BlackBerry messaging and browsing were felt in Europe, Asia, Africa and South America, RIM acknowledged early in the day.

At about 5 p.m. Tuesday, RIM reported that a core switch had failed and the backup system failed as well somewhere in RIM’s global infrastructure. When the failover system did not function, RIM said a backlog of data was generated, and noted that the company was working to clear it.

Perhaps clearing out the global backlog was causing problems in various areas Wednesday, analysts said, although RIM could not be reached to comment early.

The outages and problems caused some Twitter humour to spread. One tweet read : “it’s so thoughtful of BlackBerry to honour Steve Jobs by having two days of silience 😛 ” Another : “What did one Blackberry users say to another?? Absolutely Nothing…I am here all week…on my self…alone.”

Leave a Reply

Your email address will not be published. Required fields are marked *

Post comment