BlackBerry Outage Spreads To US

Posted: Oct 12 2011, 9:54am CDT | by , Updated: Oct 12 2011, 9:57am CDT, in News | Mobile Phones

BlackBerry Outage spreads to US

BlackBerry owners around the world are experiencing outages for their email service. Now RIM says the issue spreads to the Americas.

RIM could not choose a better timing for their service outage than the iPhone 4S launch time. I see already tons of employees whining in front of their bosses that their BlackBerry sucks and that they need an iPhone 4S. "Hey, Boss! The iPhone 4S comes with iMessage." The last three days the BlackBerry owners in Europe, Middle East and Africa had issues. RIM said that the problem is caused by a core switch failure. The back-up switch did not work as tested for the failover situation.

This sounds to be a complicated problem, as RIM is not able to fix it within days. The last update from RIM is that the issues are now spreading to the Americas.

The Update reads: "BlackBerry subscribers in the Americas may be experiencing intermittent service delays this morning. We are working to resolve the situation as quickly as possible and we apologize to our customers for any inconvenience. We will provide a further update as soon as more information is available."

You can get the latest updates on the BlackBerry outage situation here. To get educated where you can get an iPhone 4S at launch, check out our iPhone 4S News.

This story may contain affiliate links.


Find rare products online! Get the free Tracker App now.

Download the free Tracker app now to get in-stock alerts on Pomsies, Oculus Go, SNES Classic and more.

Latest News


The Author

<a href="/latest_stories/all/all/2" rel="author">Luigi Lugmayr</a>
Manfred "Luigi" Lugmayr () is the founding Chief Editor of I4U News and brings over 25 years experience in the technology field to the ever evolving and exciting world of gadgets, tech and online shopping. He started I4U News back in 2000 and evolved it into vibrant technology news and tech and toy shopping hub.
Luigi can be contacted directly at ml[@]




comments powered by Disqus