YA96871 | Service Restored | Yammer inaccessible | 3/18/2017 7:10 PM UTC

Title: Yammer inaccessible

User Impact: Users may have been unable to access the Yammer service.

Final status: We’ve monitored service health and confirmed that service has been restored and that additional restoration actions are not needed.

Scope of impact: A few customers reported the issue and we suspect that any user may have been affected by this event.

Start time: Saturday, March 18, 2017, at 5:46 PM UTC

End time: Saturday, March 18, 2017, at 7:10 PM UTC

Preliminary Root Cause: Components that facilitate access to the Yammer service were not processing traffic as expected, resulting in service impact.

Next steps:
– We’re further investigating data associated with the affected components to identify what caused the components to become degraded.

This is the final update for the event.

Posted in Service Interruption

YA96871 | Restoring Service | Yammer inaccessible | 3/18/2017 7:30 PM UTC

Title: Yammer inaccessible

User Impact: Users may be unable to access the Yammer service.

Current status: We’ve routed traffic away from the affected components to restore service. The Yammer service is currently available and we’re monitoring service health to determine if additional restoration actions are needed. Restarting specific system services associated with the affected components did not mitigate the problem.

Scope of impact: While we’re not aware of any customer reports at this time, we suspect that all users may be affected by this event.

Start time: Saturday, March 18, 2017, at 5:46 PM

Preliminary Root Cause: Components that facilitate access to the Yammer service are not processing traffic as expected, resulting in service impact.

Next update by: Saturday, March 18, 2017, at 9:00 PM UTC

Posted in Service Interruption

YA96871 | Service Degradation | Yammer inaccessible | 3/18/2017 6:46 PM UTC

Title: Yammer inaccessible

User impact: Users may be unable to access the Yammer service.

Current status: We suspect that components that facilitate access to the Yammer service are not processing traffic as expected. We’re restarting specific system services associated with the affected components in an effort to provide relief. In parallel, we continue to review service logs to confirm what is causing the problem.

Scope of impact: While we’re not aware of any customer reports at this time, we suspect that all users may be affected by this event.

Start time: Saturday, March 18, 2017, at 8:30 AM UTC

Next update by: Saturday, March 18, 2017, at 8:30 PM UTC

Posted in Service Interruption

YA96871 | Service Degradation | Yammer inaccessible | 3/18/2017 6:00 PM UTC

Title: Yammer inaccessible

User Impact: Users may be unable to access the Yammer service.

Current status: We’re analyzing log data and update history in an effort to determine what is causing the problem.

Scope of impact: While we’re not aware of any customer reports at this time, we suspect that all users may be affected by this event.

Next update by: Saturday, March 18, 2017, at 7:00 PM UTC

Posted in Service Interruption

YA96615 | Service Restored | Can’t access Yammer | 3/16/2017 07:51 PM UTC

Title: Can’t access Yammer

User impact: Users may have been unable to access Yammer

Final status: We’ve identified that a caching issue on infrastructure that facilitates access to the Yammer service may have prevented users from accessing the service. We’ve deployed a fix to resolve the underlying issue and have confirmed that service has restored. Additionally, we’ve identified that your users may see incorrect group member counts for the next hour until the fix propagates through the affected environment.

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

Start time: Thursday, March 16, 2017, at 6:42 PM UTC

End time: Thursday, March 16, 2017, at 7:30 PM UTC

Preliminary root cause: A caching issue on infrastructure that facilitates access to the Yammer service may have prevented users from accessing the service.

Next steps:
– We’re reviewing our infrastructure caching procedures to find ways to prevent this problem from happening again.

This is the final update for the event.

Posted in Service Interruption

YA96615 | Service Degradation | Can’t access Yammer | 3/16/2017 07:15 PM UTC

Title: Can’t access Yammer

User impact: Users may be unable to access Yammer

Current status: We’ve identified that systems which facilitate access to the Yammer service are degraded. We’re working to isolate the underlying issue and are investigating options to provide relief.

Scope of impact: While we’re not aware of any customer reports of impact, our monitoring indicates that any user attempting to access Yammer may be affected.

Start time: Thursday, March 16, 2017, at 6:42 PM UTC

Next update by: Thursday, March 16, 2017, at 9:00 PM UTC

Posted in Service Interruption

YA96615 | Investigating | Can’t access Yammer | 3/16/2017 06:58 PM UTC

Title: Can’t access Yammer

User impact: Users may be unable to access Yammer

Current status: We’re investigating an issue in which some users may be unable to access the Yammer service. 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: Thursday, March 16, 2017, at 6:42 PM UTC

Posted in Service Interruption