Final Status: Engineers identified that a messaging database was experiencing higher than expected utilization. To mitigate impact, engineers ended low priority server tasks that were causing the utilization spikes and performed tests to validate mitigation.
User Experience: Affected users may have experienced intermittent failures or delays when accessing the Yammer feed. In addition, new messages may not have posted as expected.
Customer Impact: This incident was resolved with little to no impact to customers. No customer reports of the issue were identified during the incident.
Incident Start Time: Tuesday, July 21, 2015, at 9:20 PM UTC
Incident End Time: Tuesday, July 21, 2015, at 9:26 PM UTC
Preliminary Root Cause: A Yammer messaging database was experiencing higher than expected utilization as certain low priority tasks were consuming more resources than expected.
Next Steps: The following is a list of known action item(s) associated with this incident. As part of the Office 365 problem management process, additional engineering actions may be identified to improve the overall service.
– Action: Further investigate the underlying cause of the issue and implement a solution to prevent future reoccurrences.
Please consider this service notification the final update on the event.