YA | Service Restored | Performance issues with Avatars and File Operations | 6/30/2015 11:21 PM UTC

Final Status: Engineers have connected the affected services to an alternate network capacity, which has remediated impact.

User Experience: Affected users may have been experiencing slowness when loading Avatars and uploading and downloading files.

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

Incident Start Time: Tuesday, June 30, 2015, at 2:45 PM UTC

Incident End Time: Tuesday, June 30, 2015, at 11:00 PM UTC

Preliminary Root Cause: A dependent third-party network experienced an interruption to connectivity, which caused impact to the Yammer infrastructure. 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: Review network routing to avoid communication interruptions related to third party network connectivity.

Please consider this service notification the final update on the event.

Posted in Service Interruption

YA25500 | Degraded | Performance issues with Avatars and File Operations | 6/30/2015 8:25 PM UTC

Current Status: Engineers have determined this issue is due to an ongoing physical network connectivity issue between Yammer and a third-party network infrastructure and are working to connect the affected service to an alternate network capacity in an effort to restore service.

User Experience: Affected users may experience slowness when loading Avatars and uploading and downloading files.

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

Incident Start Time: Tuesday, June 30, 2015, at 6:33 PM UTC

Preliminary Root Cause: A dependent third-party network experienced an interruption to connectivity, which caused impact to the Yammer infrastructure.

Next Update by: Tuesday, June 30, 2015, at 11:30 PM UTC

Posted in Service Interruption

YA25500 | Degraded | Performance issues with Avatars and File Operations | 6/30/2015 7:15 PM UTC

Current Status: Engineers are performing live diagnostics and troubleshooting the Yammer infrastructure to determine the root cause of this issue.

User Experience: Affected users may experience slowness when loading Avatars and uploading and downloading files.

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

Incident Start Time: Tuesday, June 30, 2015, at 6:33 PM UTC

Next Update by: Tuesday, June 30, 2015, at 8:30 PM UTC

Posted in Service Interruption

YA25500 | Investigating | Performance issues with Avatars and File Operations | 6/30/2015 6:40 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 experience slowness when loading Avatars and uploading and downloading files.

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

Posted in Service Interruption

YA25039 | Service Restored | Unable to use Windows Notifier version 1.0.0.457 | 6/18/2015 10:18 PM UTC

Final Status: Engineers have determined that abnormally high activity was likely responsible for this issue and monitored system load to validate mitigation. Additionally, engineers re-enabled a subset of the components that facilitate the functionality of a specific version of Windows Notifier.

User Experience: Affected users may have been unable to use Windows Notifier version 1.0.0.457.

Customer Impact: Customer impact appeared to be limited during this event. As a workaround, engineers recommended upgrading Windows Notifier to the latest version, 1.0.0.589, which is available for download here: https://about.yammer.com/product/desktop-application/

Incident Start Time: Thursday, June 18, 2015, at 3:20 PM UTC

Incident End Time: Thursday, June 18, 2015, at 9:27 PM UTC

Preliminary Root Cause: High resource utilization on a portion of capacity that facilitates network traffic may have caused impact to the affected build. The underlying root cause is still 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: Investigate resource utilization patterns and automated recovery options to prevent reoccurrence of the issue.

Please consider this service notification the final update on the event.

Posted in Service Interruption

YA25024 | Service Restored | Unable to sign in to Yammer | 6/18/2015 02:31 AM UTC

Final Status: Engineers confirmed that a network device experienced a temporary failure. Engineers took corrective actions to restart the affected network device, which restored service.

User Experience: Affected users may have been unable to sign in to Yammer.

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

Incident Start Time: Thursday, June 18, 2015, at 1:05 AM UTC

Incident End Time: Thursday, June 18, 2015, at 1:15 AM UTC

Preliminary Root Cause: A network device became temporarily degraded. The underlying root cause is still 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

YA24674 | Service Restored | Affected users may be unable to utilize Yammer Desktop Notifier. | 6/13/2015 05:13 AM UTC

Final Status: Engineers created additional database capacity, which has allowed engineers to re-enabled the Yammer Desktop Notifier for all users.

User Experience: Affected users may have been unable to use the Yammer Desktop Notifier.

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

Incident Start Time: Tuesday, June 9, 2015, at 3:36 AM UTC

Incident End Time: Friday, June 12, 2015, at 10:00 PM UTC

Preliminary Root Cause: The Yammer Desktop Notifier service encountered a spike in database usage.

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: Investigate resource utilization patterns and automated recovery options to prevent reoccurrence of the issue.

Please consider this service notification the final update on the event.

Posted in Service Interruption