YA73127 | Service Restored | Users may have been intermittently unable to sign in to Yammer. | 7/26/2016 10:24 PM UTC

Final Status: We determined that a portion of server infrastructure that facilitates Yammer sign in had become degraded. We applied a fix and confirmed service restoration.

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

Scope of Impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that a subset of your users attempting to access the service may have been affected.

Start Time: Tuesday, July 26, 2016, at 8:10 PM UTC

End Time: Tuesday, July 26, 2016, at 9:41 PM UTC

Preliminary Root Cause: A portion of server infrastructure that facilitates Yammer sign in had become degraded.

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

This is the final update for the event.

Posted in Service Interruption

YA73127 | Investigating | Users may be intermittently unable to sign in to Yammer and may receive an error message. | 7/26/2016 10:04 PM 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.

User Impact: Users may be intermittently unable to sign in to Yammer and may receive an error message. As the issue is intermittent by nature, subsequent login attempts might be successful.

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.

Posted in Service Interruption

YA72511 | Service Restored | Users may have found that Search and Autocomplete operations were not completing. | 7/15/2016 02:38 PM UTC

Final Status: We’ve identified that a portion of infrastructure that facilitates Search and Autocomplete became degraded. We restarted the affected portion of infrastructure which mitigated impact.

User Impact: Users may have found that Search and Autocomplete operations were not completing.

Scope of Impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that users may have found that Search and Autocomplete operations were not completing.

Start Time: Friday, July 15, 2016, at 12:15 PM UTC

End Time: Friday, July 15, 2016, at 1:55 PM UTC

Preliminary Root Cause: A portion of infrastructure that facilitates Search and Autocomplete 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

YA72511 | Service Degradation | Users may find that Search and Autocomplete operations are not completing. | 7/15/2016 01:23 PM UTC

Current Status: We’re analysing service log files to determine the root cause and identify steps to remediate impact.

User Impact: Users may find that Search and Autocomplete operations are not completing.

Scope of Impact: While we’re not aware of any customer reports of impact, our monitoring indicates that users may find that Search and Autocomplete operations are not completing.

Start Time: Friday, July 15, 2016, at 12:15 PM UTC.

Next Update by: Friday, July 15, 2016, at 3:30 PM UTC.

Posted in Service Interruption

YA72511 | Investigating | Users may find that Search and Autocomplete operations are not completing. | 7/15/2016 12:15 PM UTC

Current Status: We’re investigating an issue in which some users may find that Search and Autocomplete operations are not completing.

Posted in Service Interruption

YA72010| Service Restored | Users may have been unable to retrieve any results using the search functionality if the searched term matched any files hosted in private groups. However, the files were still accessible through thread and direct URL access. | 7/7/2016 02:20 PM UTC

Final Status: We’ve deployed the fix and mitigated impact.

User Impact: Users may have been unable to retrieve any results using the search functionality if the searched term matched any files hosted in private groups. However, the files were still accessible through thread and direct URL access.

Scope of Impact: While we’re not aware of any customer reports of impact, our monitoring indicates only specific file terms that have been shared in private conversation were affected.

Start Time: Tuesday, June 28, 2016, at 11:45 AM UTC

End Time: Thursday, July 7, 2016, at 1:30 PM UTC

Preliminary Root Cause: A recent build update caused impact to search functionality.

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

YA71715 | Service Restored | Users may have been unable to create or update Yammer posts. | 7/1/2016 4:10 PM UTC

Final Status: We’ve identified an issue that may have briefly prevented users from posting messages to Yammer. It was determined that a database migration caused several service components that facilitate message posting to become degraded. We halted the migration and confirmed that the service is now functioning as expected.

User Impact: Users may have been unable to create or update Yammer posts.

Scope of Impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that many users were unable to post messages to Yammer for the duration of the incident.

Start Time: Friday, July 1, 2016, at 3:59 PM UTC

End Time: Friday, July 1, 2016, at 4:10 PM UTC

Preliminary Root Cause: A database migration caused service components that facilitate message posting to become degraded, preventing some users from being able to post messages to Yammer.

Next Steps:
– We’re reviewing our deployment and migration procedures to help prevent this kind of problem in the future.

This is the final update for the event.

Posted in Service Interruption