Tag: outagePage 2 of 2

Fire at RIM shuts down Philippine BlackBerry service

Comments

FireBlackBerry users in the Philipines have reported a service outage due to a small fire at RIM. Smart Communications was the affected carrier, so we presume it was a fairly localized incident that won’t be hurting other services any time soon, but it still makes us a bit jumpy to think about what would happen if a more widespread physical danger were to come to RIM’s servers.

Smart said the problem was detected Wednesday morning. The company added that RIM’s technical personnel are currently working to re-route traffic and expects normal services soon. Another advisory said that Smart and RIM are testing a solution to bring the push e-mail service back online.

Share:
  • Twitter
  • StumbleUpon
  • LinkedIn
  • Facebook
  • del.icio.us
  • Digg
  • Reddit
  • Slashdot
  • Technorati
  • NewsVine
  • email

BlackBerry Cool Podcast: Episode 10

Comments

BBCoolBBCool Simon runs down the week’s news in an unprecedented bout of continuity. We go over the BIS outage earlier this week, RIM’s upcoming third quarter results in light of the iPhone, new studies showing BlackBerry use is getting out of hand, and more. Take a listen! (12 minutes)

Share:
  • Twitter
  • StumbleUpon
  • LinkedIn
  • Facebook
  • del.icio.us
  • Digg
  • Reddit
  • Slashdot
  • Technorati
  • NewsVine
  • email

Another BIS outage

Comments

RIMRobb’s reporting on another BlackBerry Internet Service outage, and aptly noting that we’ve had one just about every month for the last while. Everything’s all stabilized now, but users worldwide had been out of service from about 6 – 11 PM last night. I would hazard a guess that the hefty snowfall in our neighbourhood had a little something to do with the blackout, but who knows what’s going on behind RIM’s closed server room doors? Regardless of the reasons, BIS subscribers are quickly losing patience with the repeated service interruptions.

Share:
  • Twitter
  • StumbleUpon
  • LinkedIn
  • Facebook
  • del.icio.us
  • Digg
  • Reddit
  • Slashdot
  • Technorati
  • NewsVine
  • email

20 minute outage this Sunday?

Comments

RIMStefano has heard of a potential outage for the Americas and Asia-Pacific on the 25th. for 20 minutes sometime between 12:00 AM EST and 3:00 AM EST due to a firmware update. Not long, but a little warning never hurts. Too bad we have to resort to newsgroups to get this kind of information, huh? Affected services include:

* BlackBerry Enterprise Servers (BES) may be unable to connect to the BlackBerry Infrastructure during the maintenance. I recommend that nobody even log on to any of the 4 BES servers during this time as you may experience issues relating to the maintenance.
* Users may be unable to send or receive any email messages during the maintenance.
* Users may also be unable to register their device, roam in another location, or use other services such as Internet browsing or Blackberry Messenger.
* Devices may not receive new service books during the maintenance.
* Enterprise Activations may not work during this maintenance.
* PIN to PIN messaging may not work during this maintenance.

Stressed out that you’re going to be cut off? Well, if you’re BlackBerrying at 3:00 AM on a Sunday, maybe that’s the first sign you need a break anyway.

UPDATE: New info suggests the outage isn’t going to happen anymore. And this, my friends, is why we have a Rumors file.

Share:
  • Twitter
  • StumbleUpon
  • LinkedIn
  • Facebook
  • del.icio.us
  • Digg
  • Reddit
  • Slashdot
  • Technorati
  • NewsVine
  • email

Some Australian BlackBerrys down

Comment

AustraliaOptus customers down under might be having some connectivity issues today. An official statement has confirmed the issue:

“I can confirm that some Optus customers have today been experiencing disruption to their BlackBerry data services,” an Optus spokeswoman said. “Technicians have now resolved the issue and we have been progressively restoring customers to normal service from approximately 1pm (AEDT) this afternoon. Optus apologises for any inconvenience caused to its customers by this disruption.”

Any of our readers still having problems?

Share:
  • Twitter
  • StumbleUpon
  • LinkedIn
  • Facebook
  • del.icio.us
  • Digg
  • Reddit
  • Slashdot
  • Technorati
  • NewsVine
  • email

Service slowdown yesterday

Comments

AngerThere were reports yesterday of yet another BlackBerry-wide outage, ranging from a 15 minute delay in message delivery to the better part of a day. BIS and most e-mail was affected, but .blackberry.net addresses were still running smoothly. At this point, folks are getting pretty frustrated with intermittent BlackBerry service, especially when companies depend on it to keep business moving. Unless RIM can get a handle on expanding to accommodate rising traffic, or properly testing their software updates before installing them, or whatever the problem is at their end, people will start switching devices. Is anyone still having problems?

Share:
  • Twitter
  • StumbleUpon
  • LinkedIn
  • Facebook
  • del.icio.us
  • Digg
  • Reddit
  • Slashdot
  • Technorati
  • NewsVine
  • email

UPDATED: BIS service hiccup on Friday

Comments

RIMThere were reports on the 7th. of a slowdown or full-on blackout of BlackBerry Internet Service e-mail across several carriers and countries. About half of BlackBerry users were affected for up to 8 hours. All’s well now, of course, but the memory of the major outage last spring is still fresh in many people’s minds and has them concerned for RIM’s service stability. Information on network status was still solely through carriers, even when the problem was on RIM’s end. What do you think, guys? Is it RIM’s responsibility to communicate to the end users in these situations, or should their attention be entirely on the carrier? It seems silly to have to wait to get information second-hand from your service provider, when a single page on RIM’s website could save people some confusion…

UPDATE: Here we are Tuesday, and we’re still getting scattered reports of BlackBerry outage. Whether this is just because of struggling to keep up with the backlog or things are still busted from the initial crash is anybody’s guess.

Share:
  • Twitter
  • StumbleUpon
  • LinkedIn
  • Facebook
  • del.icio.us
  • Digg
  • Reddit
  • Slashdot
  • Technorati
  • NewsVine
  • email