YA22921 | Scheduled Maintenance | 5/30/2015 at 5:00 PM UTC

Maintenance window: 5:00 PM UTC Saturday, May 30, 2015 to 7:00 PM UTC Saturday, May 30, 2015
Activities: Upgrade of BIRD networking software
Potential user impact: Yammer.com site may be unreachable or slow to load while the software upgrade takes place

Posted in Scheduled Maintenance

YA22734 | Restoring Service | Unable to see suggested users in Yammer | 5/22/2015 12:50 AM UTC

Current Status: The deployment of the fix is currently ongoing. The suggested users functionality for “Pending User” has been re-enabled. Throughout the deployment of the fix, users will experience a continuous improvement of the suggested users feature.

User Experience: Users will not see suggested users to follow in Yammer.

Customer Impact: Customer impact appears to be limited at this time. Yammer functionality outside of suggested users is unaffected.

Incident Start Time: Monday, May 18, 2015, at 2:48 PM UTC

Preliminary Root Cause: A recent infrastructure update intended to improve Yammer stability has caused a portion of capacity that facilitates user suggestions for the Yammer service to not process data as expected.

Next Update by: Tuesday, May 26, 2015, at 12:00 AM UTC

Posted in Service Interruption

YA22734 | Service Degradation | Unable to see suggested users in Yammer | 5/21/2015 8:00 PM UTC

Current Status: The deployment of the fix is currently ongoing. Engineers expect that the “Pending User” functionality should begin to work as expected shortly. As the deployment continues, the remaining functionality of the suggested users feature will progressively improve.

User Experience: Users will not see suggested users to follow in Yammer.

Customer Impact: Customer impact appears to be limited at this time. Yammer functionality outside of suggested users is unaffected.

Incident Start Time: Monday, May 18, 2015, at 2:48 PM UTC

Preliminary Root Cause: A recent infrastructure update intended to improve Yammer stability has caused a portion of capacity that facilitates user suggestions for the Yammer service to not process data as expected.

Next Update by: Friday, May 22, 2015, at 2:00 AM UTC

Posted in Service Interruption

YA22825 | Service Restored | Unable to receive notifications via the Yammer Desktop Notifier application for Windows | 5/21/2015 02:02 AM UTC

Final Status: An influx of messages caused some end-point servers to become unresponsive. To remediate impact, engineers restarted the affected servers and confirmed that service had been restored.

User Experience: Affected users may have been unable to receive notifications via the Yammer Desktop Notifier application for Windows.

Customer Impact: Customer impact appears to have been limited.

Incident Start Time: Wednesday, May 20, 2015, at 10:32 PM UTC

Incident End Time: Thursday, May 21, 2015, at 12:50 AM UTC

Preliminary Root Cause: End-point servers were disabled after a large number of messages were being processed simultaneously. 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.

Posted in Service Interruption

YA22820 | Service Restored| Unable to access the Yammer service| Wednesday, May 20, 2015, at 11:10 PM UTC

Final Status: Engineers corrected a network misconfiguration to mitigate impact.

User Experience: Affected users may have been unable to access the Yammer service.

Customer Impact: Customer impact appears to have been limited.

Incident Start Time: Wednesday, May 20, 2015, at 9:55 PM UTC

Incident End Time: Wednesday, May 20, 2015, at 10:32 PM UTC

Preliminary Root Cause: A hardware capacity appeared to have a network misconfiguration. The underlying root cause of this issue 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.

Posted in Uncategorized

YA22820 | Service Degradation | Unable to access the Yammer service| 5/20/2015 at 10:00 PM UTC

Current Status: Engineers are parsing Yammer service logs and analyzing infrastructure health in an effort to identify the underlying cause of the issue.

User Experience: Affected users may be unable to access the Yammer service.

Customer Impact: The issue appears to be intermittent. Impact is limited at this time.

Incident Start Time: Wednesday, May 20, 2015, at 9:55 PM UTC

Next Update by: Wednesday, May 20, 2015, at 11:30 PM UTC

 

Posted in Service Interruption

YA22091: Maintenance Window Cancelled

Following successful migration of Yammer to Microsoft datacenters this planned contingence change window is no longer required.

Posted in Scheduled Maintenance