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

YA24674 | Service Degraded | Affected users may be unable to use Yammer Desktop Notifier | June 11, 2015, at 4:45 PM UTC

Current Status: Engineers continue to analyze diagnostic data in their effort to identify the underlying root cause. The analysis of this data is expected to take an extended period of time.

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

Customer Impact: Customer impact appears to be limited at this time. Yammer Desktop Notifier has been enabled for the majority of the affected users.

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

Next Update by: Thursday, June 18, 2015, at 5:00 PM UTC

Posted in Service Interruption

YA24674 | Service Degraded – Affected users may be unable to utilize Yammer Desktop Notifier. | June 9, 2015, at 3:36 PM UTC

Current Status: Engineers are enabling advanced logging in an effort to further isolate the underlying root cause of the issue.

User Experience: Affected users may be unable to utilize Yammer Desktop Notifier.

Customer Impact: Customer impact appears to be limited at this time. Yammer Desktop Notifier has been enabled for the majority of the affected users.

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

Next Update by: Thursday, June 11, 2015, at 5:00 PM UTC

Posted in Service Interruption

YA24674 | Service Degraded – Affected users may be unable to utilize Yammer Desktop Notifier. | June 9, 2015, at 3:36 PM UTC

Current Status: Engineers continue to investigate the issue in an effort to restore the Yammer Desktop Notifier functionality for the remaining affected users.

User Experience: Affected users may be unable to utilize Yammer Desktop Notifier.

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

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

Next Update by: Wednesday, June 10, 2015, at 5:00 PM UTC

Posted in Service Interruption

YA24674 | Service Degraded – Affected users may be unable to utilize Yammer Desktop Notifier. | June 9, 2015, at 3:36 PM UTC

Current Status: Engineers have successfully enabled Yammer Desktop Notifier for approximately 80% of the affected users and are working on fully restoring Yammer Desktop Notifier for the remaining users.

User Experience: Affected users may be unable to utilize Yammer Desktop Notifier.

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

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

Next Update by: Tuesday, June 9, 2015, at 10:00 PM UTC

Posted in Service Interruption