Final Status: The investigation determined that an update to the environment caused a portion of infrastructure responsible for Yammer feeds to become degraded. Engineers rolled out a fix throughout the affected environment, which remediated impact.
User Experience: Affected users may have been unable to load ‘All-company’ and ‘All’ feeds.
Customer Impact: Analysis indicates that customers will likely have few, if any, users experiencing impact related to this event. No customer reports of the issue have been identified at this time.
Incident Start Time: Tuesday, September 22, 2015, at 1:32 PM UTC
Incident End Time: Tuesday, September 22, 2015, at 2:00 PM UTC
Preliminary Root Cause: As part of our efforts to improve service performance, an update was deployed to the affected infrastructure; however, the update caused a code issue which resulted in impact.
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: Review the infrastructure update process to prevent reoccurrences of this scenario.
– Action: Review procedures for validating service updates as a code bug was not identified during the testing phase of the development process.
Please consider this service notification the final update on the event.