YA82214 | Service Restored | Unable to sign in to Yammer. | 10/21/2016 02:07 PM UTC

Title: Unable to sign in to Yammer.

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

Final status: We’ve updated the DNS configuration, which has remediated impact.

Scope of impact: A few customers reported this issue, and our analysis indicated that customers with a managed DNS service were more likely to be impacted.

Start time: Friday, October 21, 2016, at 11:55 AM UTC.

End time: Friday, October 21, 2016, at 1:20 PM UTC.

Preliminary root cause: Issues with DNS resolution was impacting availability of the service.

Next steps:
– We’re reviewing our monitoring services to find ways to reduce detection time and to improve our automated recovery processes.

We’ll publish a post-incident report within five business days.

Posted in Service Interruption

YA82176 | Service Restored | Unable to sign in to Yammer. | 10/21/2016 09:06 AM UTC

Title: Unable to sign in to Yammer.

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

Final status: We’ve identified that connectivity issues between networking and sign-in components was causing impact to the service. We’ve reset connectivity sessions to remediate impact.

Scope of impact: A few customers reported this issue, and our analysis indicated that this issue may have potentially affected any of your users attempting to use the Yammer service.

Start time: Friday, October 21, 2016, at 7:55 AM UTC.

End time: Friday, October 21, 2016, at 8:10 AM UTC.

Preliminary root cause: Connectivity issues between networking and sign-in components was causing impact to the service.

Next steps:
– We’re analysing 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

YA81925 | Service Restored | Can’t sign into Yammer. | 10/20/2016 09:15 AM UTC

Title: Can’t sign into Yammer.

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

Final status: We’ve identified that there were connectivity issues between networking and sign-in components. We reset connectivity sessions, which remediated impact.

Scope of impact: A few customers reported this issue, and our analysis indicated that this issue may have potentially affected any of your users attempting to use the Yammer service.


Start time: Thursday, October 20, 2016, at 7:10 AM UTC

End time: Thursday, October 20, 2016, at 8:08 AM UTC

Preliminary root cause: There were connectivity issues between networking and sign-in components.

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

YA81490 | Service Restored | Can’t view feeds and messages | 10/14/2016 10:54 PM UTC

Title: Can’t view feeds and messages

User impact: Users may have been unable to see Yammer feeds and messages.

Final status: We’ve determined that a recent configuration change caused a portion of the infrastructure that facilitates Yammer messaging functionality became degraded. We’ve reverted this change, which has fixed the issue. 

Scope of impact: While we’re not aware of any customer reports at this time, we’re reviewing monitoring alerts to check for potential impact to your users.

Start time: Friday, October 14, 2016, at 9:16 PM UTC

End time: Friday, October 14, 2016, at 9:45 PM UTC

Preliminary root cause: A portion of the infrastructure that facilitates Yammer messaging functionality became degraded causing impact to messaging and feeds.

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

YA81490 | Investigating | Can’t view feeds and messages | 10/14/2016 09:53 PM UTC

Title: Can’t view feeds and messages

User impact: Users may be unable to see Yammer feeds and messages.

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: While we’re not aware of any customer reports at this time, we’re reviewing monitoring alerts to check for potential impact to your users.

Start time: Friday, October 14, 2016, at 9:16 PM UTC

Posted in Service Interruption

YA80898 | Service Restored | Users may have seen blank or partial message feeds. | 10/10/2016 03:28 PM UTC

Final status: We’ve identified an issue that caused impact to message feeds and determined that a portion of infrastructure that processes message requests performed below acceptable thresholds. We deployed a code fix to remediate the high search requests load on the affected infrastructure and verified impact has been mitigated.

Scope of impact: While we weren’t aware of any customer reports of impact, our monitoring indicates that the issue may have potentially affected any of your users attempting to view message feeds.

Start time: Monday, October 10, 2016, at 1:38 PM UTC

End time: Monday, October 10, 2016, at 2:18 PM UTC

Preliminary root cause: A portion of infrastructure that processes message requests performed below acceptable thresholds.

Next steps:
– We’re reviewing our code for optimizations and automated recovery options to prevent this kind of problem from reoccurring.

This is the final update for the event.

Posted in Service Interruption

YA80763 | Service Restored | Users may have experienced delays when sending or receiving messages or updating feeds through Yammer. | 10/7/2016 02:28 AM UTC

Final status: We’ve restarted the affected infrastructure and confirmed that the service is healthy.

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

Start time: Friday, October 7, 2016, at 1:33 AM UTC

End time: Friday, October 7, 2016, at 1:57 AM UTC

Preliminary root cause: Infrastructure responsible for processing message requests was in an unresponsive state.

Next steps:
– We’ll continue to monitor the service while we develop preventative actions to stop this issue from occurring again.

This is the final update for the event.

Posted in Service Interruption