YA15744| Service Restored| Message post delays| Thursday, February 26, 2015 at 8:10 PM UTC

Final Status: Engineers added additional capacity to assist with message processing and impact was successfully remediated.

User Experience: Affected users may have experienced delays of up to five minutes when posting a new message.

Customer Impact: Impact was limited throughout the duration of the incident.

Incident Start Time: Thursday, February 26, 2015, at 7:52 PM UTC

Incident End Time: Thursday, February 26, 2015, at 8:10 PM UTC

Preliminary Root Cause: A database within a portion of Yammer capacity that facilities message processing was not functioning as expected. The underlying cause of the issue is still under investigation.

Next Steps: The following is a list of known action item(s) associated with this incident. As part of the problem management process, additional actions may be identified to improve the overall service.
– Action: Further investigate 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

YA15242 | Service Restored| File preview rendering issue | Thursday, February 12, 2015, at 5:55 AM UTC

Final Status: Engineers successfully implemented a configuration modification on a subset of Yammer servers to remediate impact.

User Experience: Affected users were unable to render file preview correctly within the user interface.

Customer Impact: A few customers reported that they experienced impact throughout the duration of the incident. The issue was specific filenames that contained spaces. Files with names without spaces rendered in file preview as expected.

Incident Start Time: Friday, February 6, 2015, at 12:00 PM UTC

Incident End Time: Thursday, February 12, 2015, at 5:55 AM UTC

Preliminary Root Cause: A configuring issue on a subset of Yammer servers prevented the file preview feature from functioning as expected.  The underlying cause of the issue is still under investigation.

Next Steps: The following is a list of known action item(s) associated with this incident. As part of the problem management process, additional actions may be identified to improve the overall service.
– Action: Review the infrastructure update process to prevent reoccurrences of this scenario.

Posted in Service Interruption

YA15242 | Service degradation | File preview rendering issue | Wednesday, February 11, 2015, at 11:45 PM UTC

Current Status: Engineers are deploying additional metrics intended to gather logs for analysis to determine a root cause. Additionally, engineers are exploring viable workarounds to allow file preview rendering to continue during the remediation process.

User Experience: Affected users are unable to render file preview correctly within the user interface.

Customer Impact: A few customers are reporting that they are experiencing this issue.

Incident Start Time: Friday, February 6, 2015, at 12:00 PM UTC

Next Update by: Friday, February 13, 2015, at 12:00 AM UTC

Posted in Service Interruption

YA15249 | Service Restored| Affected users may have experience delays of up to 45 minutes when posting messages to Yammer.com | 2/11/2015 4:05 PM UTC

Current Status: Engineers remediated end-user impact by restarting the affected component.

User Experience: Affected users may have experienced delays of up to 45 minutes when posting messages to Yammer.com.

Customer Impact: Impact was limited throughout the duration of the incident.

Incident Start Time: Wednesday, February 11, 2015, at 2:35 PM UTC

Incident End Time: Wednesday, February 11, 2015, at 4:05 PM UTC

Preliminary Root Cause: The component that processes message postings for Yammer was in an unresponsive state. The underlying cause of the issue is under investigation.

Next Steps: The following is a list of known action item(s) associated with this incident. As part of the problem management process, additional 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

YA15249 | Service Degraded| Affected users may experience delays of up to 45 minutes when posting messages to Yammer.com | 2/11/2015 2:35 PM UTC

Current Status: Currently, engineers are investigating an issue where some customers are experiencing a delay when posting messages to Yammer.com.

User Experience: Affected users are experiencing delays of up to 45 minutes when posting messages to Yammer.com

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

Incident Start Time: Wednesday, February 11, 2015, at 2:35 PM UTC

Next update: Wednesday, February 11, 2015, at 5:30 PM UTC

 

Posted in Service Interruption

YA12408 | Service Restored | Outdated data when using Autocomplete, data export, and full-text search | 2/10/2015 9:40 PM UTC

Final Status: Engineers migrated services to an alternate datacenter with upgraded resources, and rebuilt indexes on the new servers to fully remediate impact.

User Experience: The affected users may have received outdated data when using Autocomplete, data export, and full-text search functionality within Yammer.

Customer Impact: Customer impact appears to have been limited to a subset of users.

Incident Start Time: Monday, January 26, 2015, at 5:16 AM UTC

Incident End Time: Tuesday, February 10, 2015, at 9:40 PM UTC

Preliminary Root Cause: A backend component became degraded and impacted Yammer search functionality.

Next Steps: The following is a known action item associated with this incident. As part of the problem management process, additional actions may be identified to improve the overall service.
– Action: Identify what caused the backend component to become degraded and implement a solution to ensure the issue does not reoccur.

Posted in Service Interruption

YA15242 | Service Degradation | File preview rendering issue | Wednesday, February 11, 2015, at 4:43 AM UTC

Current Status: The investigation has determined that infrastructure responsible for rendering file previews is intermittently not processing requests as expected. Engineers are gathering logs for further analysis in an effort to identify the root cause.

User Experience: Affected users are unable to render file preview correctly within the user interface.

Customer Impact: A few customers are reporting that they are experiencing this issue.

Incident Start Time: Friday, February 6, 2015, at 12:00 PM UTC

Next Update by: Thursday, February 12, 2015, at 12:00 AM UTC

Posted in Service Interruption