Final Status: Engineers identified that by design, an automated recovery feature took the appropriate action to restore service health.
User Experience: Affected users may have been unable to access Yammer.com.
Customer Impact: Customer impact appeared to be limited during this event.
Incident Start Time: Wednesday, May 20, 2015, at 3:00 PM UTC
Incident End Time: Wednesday, May 20, 2015, at 3:20 PM UTC
Preliminary Root Cause: Components that facilitate load balancing across the affected environment were not performing as expected. The underlying root cause is 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.
Please consider this service notification the final update on the event.