Final Status: The investigation identified that a portion of Yammer capacity responsible for balancing traffic throughout the affected environment was not functioning as expected. Engineers implemented a configuration change to ensure that the affected infrastructure is no longer attempting to balance traffic. In addition, engineers restarted infrastructure that facilitates access to the Yammer service to mitigate impact.
User Experience: Affected users may have been unable to access the Yammer service.
Customer Impact: Impact was limited throughout the duration of the incident.
Incident Start Time: Tuesday, April 28, 2015, at 1:35 PM UTC
Incident End Time: Tuesday, April 28, 2015 at 2:25 PM UTC
Preliminary Root Cause: A database connectivity issue within the infrastructure that facilitates access to Yammer was preventing users from accessing the service. In addition, a portion of Yammer capacity responsible for balancing traffic throughout the affected environment was not functioning as 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.