YA87902 | Service Restored | Pages not loading on Internet Explorer 11 on Windows 10 | 12/7/2016 12:35 AM UTC

Title: Pages not loading on Internet Explorer 11 on Windows 10

User impact: Users may have been unable to view Yammer pages on Internet Explorer 11 on Windows 10.

Final status: We determined that a recent update is affecting Yammer page loading for Internet Explorer 11 users on Windows 10. We’ve reverting the update in order to remediate impact.

Scope of impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that all Yammer users may have been affected.

Start time: Tuesday, December 6, 2016, at 10:02 PM UTC

End time: Tuesday, December 6, 2016, at 11:55 PM UTC

Preliminary root cause: A recent update to infrastructure that processes Javascript requests had degraded page loading.

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 Uncategorized

YA87457 | Service Restored | Yammer latency | 12/2/2016 10:45 AM UTC

Title: Yammer latency.

User impact: Users may have experienced latency when using the Yammer service.

Final status: We’ve determined that a process failure within the Yammer infrastructure caused the service to perform below acceptable thresholds. By design, an automated recovery feature moved the affected service to alternate healthy, infrastructure to restore service health.

Scope of impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that a subset of users may have been affected.

Start time: Friday, December 2, 2016, at 10:39 AM UTC

End time: Friday, December 2, 2016, at 10:45 AM UTC

This is the final update for the event.

Posted in Service Interruption

YA84891 | Service Restored | Problem posting messages. | 11/4/2016 09:09 AM UTC

Title: Problem posting messages.

User impact: Users were unable to post messages on Yammer.

Final status: We’ve identified that a component of infrastructure that facilitates database connections became degraded. By design, an automated recovery feature took the appropriate action to restore service.

Scope of impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that users would have been unable to post messages on Yammer.

Start time: Friday, November 4, 2016, at 7:15 AM UTC.

End time: Friday, November 4, 2016, at 7:45 AM UTC.

Preliminary root cause: A component of infrastructure that facilitates database connections 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

YA83423 | Service Restored | Intermittent feed issues. | 10/28/2016 06:31 PM UTC

Title: Intermittent feed issues.

User impact: Users may have been intermittently unable to load feeds.

More info: Users may have seen a grey bar and the message “Click here to reload”. After reloading, feeds may have loaded as normal.

Final status: We’ve determined that a portion of infrastructure that facilitates Yammer feed functionality became degraded. Although our initial attempt to restart the Yammer services on the affected infrastructure was unsuccessful, a second attempt was successful in resolving the issue.

Scope of impact: A few customers reported this issue, and our analysis indicated that all users were affected.

Start time: Friday, October 28, 2016, at 7:06 AM UTC

End time: Friday, October 28, 2016, at 2:55 PM UTC

Preliminary root cause: A portion of infrastructure that facilitates Yammer feed functionality became degraded.

Next steps:
– We’re analyzing performance data and trends on the affected infrastructure to help prevent feed load issues in the future.

This is the final update for the event.

Posted in Service Interruption

YA83426 | Service Degradation | Intermittent feed issues. | 10/28/2016 04:00 PM UTC

Title: Intermittent feed issues.

User impact: Users may be intermittently unable to load feeds.

More info: Users may see a grey bar and the message “Click here to reload”.

Current status: Our attempts to resolve the issue through increasing the load threshold limit for timeouts and restarting the service were unsuccessful. We’re analyzing log data from the affected environment to determine the next troubleshooting steps.

Scope of impact: A few customers have reported this issue, and our analysis indicates that all users are affected.

Start time: Friday, October 28, 2016, at 7:00 AM UTC

Next update by: Friday, October 28, 2016, at 7:00 PM UTC

Posted in Service Interruption

YA83423 | Service Degradation | Intermittent feed issues. | 10/28/2016 01:59 PM UTC

Title: Intermittent feed issues.

User impact: Users may be intermittently unable to load feeds.

More info: Users may see a grey bar and the message “Click here to reload”.

Current status: We’ve increased the load threshold limit for timeouts, and are restarting the service, to remediate impact.

Scope of impact: A few customers have reported this issue, and our analysis indicates that all users are affected.

Start time: Friday, October 28, 2016, at 7:00 AM UTC.

Preliminary root cause: We’ve identified a higher than expected load on a service that facilitates the loading of feeds.

Next update by: Friday, October 28, 2016, at 4:00 PM UTC.

Posted in Service Interruption

YA82277 | Couldn’t access yammer.com

User Impact: Users may have been unable to access yammer.com.

Final status: We’ve cleared the stale connection requests and confirmed that service has been restored.

Scope of impact: A few customers reported the issue, and our analysis indicated that any user served through the affected infrastructure would have experienced the problem.

Start time: Friday, October 21, 2016, at 3:52 PM UTC

End time: Friday, October 21, 2016, at 8:28 PM UTC

Preliminary root cause: Incoming connections to the service had become degraded on a portion of server infrastructure.

Next steps:
– We’ll continue to monitor the environment to ensure the issue does not reoccur.

This is the final update for the event.

Posted in Uncategorized