Final Status: Engineers indicated that by design, an automated recovery feature took the appropriate action to restore service health. Engineers will continue to monitor service health.
User Experience: Affected users may have been unable to access Yammer.com or may have experienced degraded performance while using the service.
Customer Impact: Customer impact appeared to be limited during this event.
Incident Start Time: Tuesday, May 12, 2015, at 3:05 PM UTC
Incident End Time: Tuesday, May 12, 2015, at 4:10 PM UTC
Preliminary Root Cause: Engineers suspect that one of the back-end services related to caching is responsible for this incident, however, the 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.