Final Status: By design, an automated recovery feature took the appropriate action to remediate impact.
User Experience: Affected users may have been unable to access Yammer services or may have experienced delays when attempting to access Yammer services.
Customer Impact: Customer impact appears to have been limited.
Incident Start Time: Sunday, May 17, 2015, at 4:35 AM UTC
Incident End Time: Sunday, May 17, 2015, at 4:37 AM UTC
Preliminary Root Cause: The Yammer service became degraded. The underlying root cause of the issue is still under investigation.
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: Identify the underlying root cause and develop a solution to prevent reoccurrences of this issue.
Please consider this service notification the final update on the event.