Update 4:47PM ET: This just in... (Also see:
Reuters update)
Update 5:08PM ET: Several PinStackers reporting restored service. No confirmation if the issues are still ongoing or resolved (more shortly).
% of Subscribers Affected: 50.00 (estimated)
Details: Affecting all carriers, intermittently. Services affected are: Email, browser, PIN messages, provisioning, BES servers may not be able to connect to RIM infrastructure.
Downtime: ongoing? (to be confirmed shortly)
Cause: to be determined
Original post:
We've had reports of BIS issues from our various contacts. I haven't been able to access mobile.blackberry.com, wap.pinstack.com or anything via BB browser recently. Anyone else experiencing issues?
We also received the following report:
Quote:
|
Verizon is stating that RIM is having network infrastructure problems right now. We're not sure if all carriers are affected. I had a BES end user who can't get service books, nor browse.
|
Quote:
Blackberry Outage
A component of the network infrastructure is experiencing a service
interruption.
Service Affected: BlackBerry All service for some *The Americas Network
(MULT) subscribers in the following locations: The Americas,
Summary: BlackBerry Network Infrastructure
Impact: BlackBerry subscribers may be unable to send or receive messages.
Subscribers may also be unable to register their device, roam in another
location, or use other services such as Internet browsing.
BlackBerry Internet Service subscribers may be unable to use the
BlackBerry Internet Service web site or perform activities such as
creating new accounts, accessing their Internet mailbox, integrating
third-party email accounts, or viewing email attachments.
Devices may not receive new service books. BlackBerry Connect and
BlackBerry-enabled devices that require a new PIN may be unable to receive
the PIN.
BlackBerry Enterprise Servers may be unable to connect to the BlackBerry
Infrastructure.
Wireless service providers and device resellers may be unable to use
BlackBerry administration web sites or perform activities such as creating
subscriber accounts or provisioning services for subscribers. [xxxxx]
Ticket Number: xxxxxxxxx
Incident Window Start Date and Time: 11 February 2008 15:20:00 (EST)
Downtime Duration: Ongoing
% of Subscribers Affected: 50.00 (estimated)
Cause: To Be Determined
EST = GMT - 5 hours
EDT = GMT - 4 hours
AEST = GMT + 10 hours
|
More shortly...