Skip to main content

Unplanned Outage: BlackBerry issue sending and receiving email

Last Updated:
2012-05-04 04:00:00
Event:
2012-05-02 04:00:00
Status:
Closed
Brief Description:
User Impact:
N/A
Workaround:
There is no workaround for this issue
Current Status:
N/A
Services Affected:
Full Description:
Beginning at 2:50 pm, BlackBerry service stopped functioning normally. We are working with Research In Motion to determine the underlying cause. The 450 users of the CIT Exchange BlackBerry Enterprise Server may not be able to send and receive email on their BlackBerry devices.
CIT TDX ID:



Timeline of Changes

Description Current Status Date Time
There have been no further disruptions to the Cornell Information Technologies BlackBerry Express service since Wednesday evening at 7:32 pm. There have been no further disruptions to the Cornell Information Technologies BlackBerry Express service since Wednesday evening at 7:32 pm. 2012-05-04 04:00:00
Between 2:21 pm and 7:32 pm on Wednesday, May 2nd, the 432 users of the BlackBerry service were unable to send and receive messages on their BlackBerry mobile devices. The underlying cause of the outage appears to be dropped connections as a result of communication failures between the Exchange CASHUB servers and Active Directory domain controllers. See also:\n\nhttp://www.it.cornell.edu/services/alert.cfm?id=1976\n\nThe problem has been temporarily resolved at 7:32 pm by moving all BlackBerry users to a secondary failover server. We will continue to work with Research in Motion on Thursday to resolve the underlying issue.\n Between 2:21 pm and 7:32 pm on Wednesday, May 2nd, the 432 users of the BlackBerry service were unable to send and receive messages on their BlackBerry mobile devices. The underlying cause of the outage appears to be dropped connections as a result of communication failures between the Exchange CASHUB servers and Active Directory domain controllers. See also:\n\nhttp://www.it.cornell.edu/services/alert.cfm?id=1976\n\nThe problem has been temporarily resolved at 7:32 pm by moving all BlackBerry users to a secondary failover server. We will continue to work with Research in Motion on Thursday to resolve the underlying issue.\n 2012-05-02 04:00:00