Performance: Outlook Web App: Difficulty Retrieving Email
Last Updated:
2014-05-02 04:00:00
Event:
2014-05-02 04:00:00
Status:
Closed
Brief Description:
Email
User Impact:
N/A
Workaround:
There is no workaround for this issue
Current Status:
N/A
Services Affected:
Full Description:
CIT is receiving reports of individuals having difficulty retrieving email using Outlook Web App. Details are being gathered and the issue is being investigated.
CIT TDX ID:
Timeline of Changes
| Description | Current Status | Date | Time |
|---|---|---|---|
| Some people affected by the issue report seeing a message "Service Unavailable: HTTP Error 503. The Service is unavailable." Other individuals who were previously unable to retrieve email through Outlook Web App have indicated that the service is now working for them again.\n\nMicrosoft is aware of the problem and has indicated that engineers are working to resolve it. | Some people affected by the issue report seeing a message "Service Unavailable: HTTP Error 503. The Service is unavailable." Other individuals who were previously unable to retrieve email through Outlook Web App have indicated that the service is now working for them again.\n\nMicrosoft is aware of the problem and has indicated that engineers are working to resolve it. | 2014-05-02 | 04:00:00 |
| Microsoft has resolved the issue. \n\n"Engineers identified an issue in which some customers may have been unable to access the Exchange Online service. Investigation determined that a portion of the mailbox capacity entered into a non-responsive state. Engineers restarted the remaining affected capacity to complete the remediation process. The issue was successfully fixed on Friday, May 2, 2014, at 7:50 PM UTC [3:50 PM Eastern Time]. Upon analysis of the incident, service impact was determined to be limited." | Microsoft has resolved the issue. \n\n"Engineers identified an issue in which some customers may have been unable to access the Exchange Online service. Investigation determined that a portion of the mailbox capacity entered into a non-responsive state. Engineers restarted the remaining affected capacity to complete the remediation process. The issue was successfully fixed on Friday, May 2, 2014, at 7:50 PM UTC [3:50 PM Eastern Time]. Upon analysis of the incident, service impact was determined to be limited." | 2014-05-02 | 04:00:00 |