YA94107 | Service Restored | Login problem | 2/20/2017 12:05 PM UTC

Title: Login problem

User impact: Users may have been unable to sign in to Yammer.

More info: While we were focussed on remediation, users may have been able to login successfully when retrying.

Final status: We’ve determined that load balancing became degraded. The load balancing services were automatically restarted, however, processes were not running as expected, causing impact. We manually corrected the processes and impact has been remediated.

Scope of impact: While we’re not aware of any customer reports at this time, we’ve identified impact was specific to the Persona service.

Start time: Monday, February 20, 2017, at 8:21 AM UTC

End time: Monday, February 20, 2017, at 11:40 AM UTC

Preliminary root cause: Load balancing became degraded.

Next steps:
– We’re analyzing performance data and trends on the affected systems to help prevent this problem from happening again.

This is the final update for the event.

Posted in Service Interruption

YA93793 | Service Restored | Yammer loading delays | 2/17/2017 12:50 AM UTC

Title: Yammer loading delays

User impact: Users may have experienced delays in accessing content in the Yammer Enterprise Service.

More info: Specifically users may have experienced delays in page loading, message posting, and message loading times in the Yammer Enterprise Service.

Final status: By design, an automated recovery feature took the appropriate action to restore service health.

Scope of impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that all users across all platforms were affected.

Start time: Friday, February 17, 2017, at 12:03 AM UTC

End time: Friday, February 17, 2017, at 12:22 AM UTC

This is the final update for the event.

Posted in Uncategorized

YA91657 – Service Restored | Double-bytes characters degrading groups/external network access | 1/24/2017 06:45 AM UTC

Title: Double-bytes characters degrading groups/external network access

User impact: Users may have been unable to access external networks that contain double-byte characters.

More info: Users may have also been unable to edit existing groups or create Yammer groups containing double-byte characters.

Final status: We’ve reverted a recent update to system performance and health monitoring, which remediated the issue. 

Scope of impact: A few customers reported this issue, and impact is specific to networks that use double-byte characters such as non-English languages.

Start time: Tuesday, January 24, 2017, at 12:30 AM UTC

End time: Tuesday, January 24, 2017, at 6:15 AM UTC

Preliminary root cause: An update to systems that facilitate the monitoring of system performance and health inadvertently degraded the service.

Next steps:
– We’re reviewing our update procedures to help catch this kind of problem during our testing cycle.

This is the final update for the event.

Posted in Service Interruption

YA91657 – Service Degradation – Users may be unable to access external networks that contain double-byte characters. 01/24/2014 5:18 AM UTC

More info: Users may also be unable to edit existing groups or create Yammer groups containing double-byte characters.

Current status: We’re continuing our initial investigating to determine the next steps required to remediate this issue.

Scope of impact: A few customers reported this issue, and impact is specific to networks that use double-byte characters such as non-English languages.

Next update by: Tuesday, January 24, 2017, at 8:30 AM UTC

Posted in Uncategorized

YA91657 – Service Degradation – Users may be unable to access external networks that contain double-byte characters. 01/24/2014 4:50 AM UTC

Current status: We’re investigating an issue in which some users may be unable to access or use Yammer services or features. We’ll provide an update shortly.

Scope of impact: A few customers reported this issue, and impact is specific to networks that use double-byte characters such as non-English languages.

Posted in Service Interruption

YA89322 – Service restored – Users may have experienced either slow loading or failures while accessing their inboxes and feeds. – 12/23/2016 6:47 AM UTC

Final status: By design, an automated recovery features rebalanced a spike in network traffic to restore service health.

Scope of impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that impact was limited to a subset of users.

Start time: Friday, December 23, 2016, at 5:57 AM UTC

End time: Friday, December 23, 2016, at 6:18 AM UTC

This is the final update for the event.

Posted in Service Interruption

YA89322 – Service Interruption – The impact to users is under investigation. – 12/23/2016 6:47 AM UTC

Title: We’re looking into a potential problem
User impact: The impact to users is under investigation.
Current status: We’ve identified a problem with the Yammer service and have confirmed that service is now restored. We’ll provide additional information in the closure summary.
Posted in Uncategorized