YA24094 | Service Restored | Unable to access Yammer.com 5/28/2015 10:30 PM UTC

Final Status: Engineers temporarily disabled a Yammer component to mitigate impact.

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

Customer Impact: Customer impact appeared to be limited during this event. Engineers have identified that users connecting from the North America region were impacted by this event.

Incident Start Time: Thursday, May 28, 2015, at 10:06 PM UTC

Incident End Time: Thursday, May 28, 2015, at 10:30 PM UTC

Preliminary Root Cause: During our efforts to add additional capacity, Yammer.com experienced performance issues.

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 the infrastructure update process as adding additional capacity caused impact to occur during a deployment.

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

 

Posted in Service Interruption

YA24094| Investigating| Unable to access Yammer.com | 5/28/2015 10:06 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. Engineers have identified that users connecting from the North America region are impacted by this event.

Posted in Service Interruption

YA22734 | Service Restored | Unable to see suggested users in Yammer | 5/28/2015 12:38 AM UTC

Final Status: Engineers have completed the deployment of the code fix, which has remediated impact.

User Experience: Users would not have seen suggested users to follow in Yammer.

Customer Impact: Customer impact appears to have been limited. Yammer functionality outside of suggested users was unaffected.

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

Incident End Time: Wednesday, May 27, 2015, at 10:15 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 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 procedures for validating service updates as the user suggestion data processing issue was not identified during the testing phase of the development process.

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

Posted in Service Interruption

YA24048| Service Restored| Message Delays | 5/27/2015 8:00 PM UTC

Final Status: Engineers added additional capacity and subsequently re-routed traffic to alternate Yammer infrastructure to mitigate impact. The message queue has cleared and there are no longer delays when sending and receiving Yammer messages.

User Experience: Affected users may have experienced delays when sending and receiving Yammer messages.

Customer Impact: Impact was limited throughout the duration of the incident. The most prominent forms of impacted messages included: message posting and replies, digests, activation and sign-up, group joins and mentions.

Incident Start Time: Wednesday, May 27, 2015, at 2:30 PM UTC

Incident End Time: Wednesday, May 27, 2015, at 8:00 PM UTC

Preliminary Root Cause: The message delivery process that the Yammer infrastructure utilizes was not functioning as expected. The underlying cause of the issue remains 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: Further investigate the underlying cause of the issue and implement a solution to prevent future occurrences.

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

 

Posted in Service Interruption

YA24048| Service Degraded| Message Delays | 5/27/2015 7:15 PM UTC

Current Status: Engineers have added additional capacity to assist with processing Yammer messages. The message queue is currently draining, though not as quickly as expected. Engineers continue to investigate a means to expedite the delivery of the messages.

User Experience: Affected users may experience delays when sending and receiving Yammer messages.

Customer Impact: Impact appears to be limited at this time. The most prominent forms of impacted messages include: message posting and replies, digests, activation and sign-up, group joins and mentions.

Incident Start Time: Wednesday, May 27, 2015, at 2:30 PM UTC

Preliminary Root Cause: The message delivery process that the Yammer infrastructure utilizes is not functioning as expected. The underlying cause of the issue remains under investigation.

Next Update by: Wednesday, May 27, 2015, at 10:00 PM UTC

Posted in Service Interruption

YA24048| Service Degraded| Message Delays | 5/27/2015 6:15 PM UTC

Current Status: Engineers have identified that Yammer messages are currently queued for delivery and are adding additional capacity to assist in processing the messages.

User Experience: Affected users may experience delays when sending and receiving Yammer messages.

Customer Impact: Impact appears to be limited at this time. The most prominent forms of impacted messages include: message posting and replies, digests, activation and sign-up, group joins and mentions.

Incident Start Time: Wednesday, May 27, 2015, at 2:30 PM UTC

Next Update by: Wednesday, May 27, 2015, at 7:30 PM UTC

Posted in Service Interruption

YA24016 | Service Restored| Unable to connect to Yammer | 5/27/2015 2:03 PM UTC

Final Status: After correcting a configuration issue on a limited portion of Yammer networking infrastructure, engineers performed tests and validated that impact was successfully mitigated.

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

Customer Impact: Customers were reporting that they were experiencing this issue.

Incident Start Time: Wednesday, May 27, 2015, at 12:00 PM UTC

Incident End Time: Wednesday, May 27, 2015, at 2:03 PM UTC

Preliminary Root Cause: A configuration issue caused a portion of the networking infrastructure that facilitates access to Yammer.com to become degraded. The underlying cause of the issue remains 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: Further investigate the underlying cause of the issue and implement a solution to prevent future occurrences.

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

Posted in Service Interruption