YA22734 | Service Degradation | Unable to see suggested users in Yammer | 5/20/2015 7:30 PM UTC

Current Status: Engineers are in the process of deploying the fix, which means that the “Pending Users” portion of the “Suggested Users” feature will become visible. Enabling full functionality of the “Suggested Users” feature is the next course of action.

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: Thursday, May 21, 2015, at 8:00 PM UTC

Posted in Service Interruption

YA22807 | Service Restored | Unable to access Yammer.com | 5/20/2015 4:20 PM UTC

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.

 

Posted in Service Interruption

YA22807 | Investigating | Unable to access Yammer.com | 5/20/2015 3:05 PM UTC

Current Status: Engineers are investigating an issue in which some users may be experiencing problems accessing or using Yammer services or features. This event is actively being investigated. More information will be provided shortly.

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

Customer Impact: Customer impact appears to be limited at this time.

Posted in Service Interruption

YA22734 | Service Degradation | Unable to see suggested users in Yammer | 5/19/2015 7:40 PM UTC

Current Status: Engineers continue to develop a solution that modifies how a portion of the Yammer infrastructure processes data. Once development of the solution is completed, it will be rigorously tested to ensure that it mitigates impact prior to deployment throughout the affected environment.  Once the deployment is initiated, the “Pending Users” portion of the suggested users feature will become visible, with the remainder of the suggested users functionality to follow.

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: Wednesday, May 20, 2015, at 8:00 PM UT

Posted in Service Interruption

Browser Caching Issue Following Data Centre Migration

If you’ve been automatically redirected here from Yammer.com, please restart your browser and attempt your navigation again.

Posted in Uncategorized

YA22734 | Service Degradation | Unable to see suggested users in Yammer | 5/19/2015 12:56 AM UTC

Current Status: Engineers have identified an issue affecting the suggested users feature in Yammer. Engineers are working on a code fix to remediate impact.

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

Customer Impact: Customer impact appears to be limited at this time.

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

Next Update by: Tuesday, May 19, 2015, at 8:00 PM UTC

Posted in Service Interruption

YA22707 | Service Restored | Unable to receive notifications via the Yammer Desktop Notifier application. | 5/19/2015 12:31 AM UTC

Final Status: Engineers deployed a fix to re-enable the affected system services, which remediated impact.

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

Customer Impact: Customer impact appeared to be limited during this event.

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

Incident End Time: Monday, May 18, 2015, at 11:27 PM UTC

Preliminary Root Cause: A portion of database capacity which facilitates the Yammer notification service for the Desktop Notifier application became degraded. 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