YA75682 | Service Restored | Admins were experiencing delays provisioning new and existing subscriptions

Final Status: We’ve confirmed that the provisioning backlog has been processed and the incident is resolved.

User Impact: End users were not affected by this issue. In earlier stages of the incident, administrators may have experienced delays when provisioning new and existing subscriptions. Affected administrators would have seen their subscriptions stuck in the “Finalizing” status. In the latter stages of the event, impact was isolated to administrators whose provisioning requests were stuck in the provisioning backlog. New provisioning requests were unaffected by this incident while the provisioning backlog was processed.

Scope of Impact: A few customers reported this issue, and our analysis indicated that any new tenants were potentially affected.

Start Time: Wednesday, August 24, 2016, at 10:00 PM UTC

End Time: Wednesday, August 31, 2016, at 2:00 PM UTC

Preliminary Root Cause: A configuration issue within the infrastructure that handles Yammer provisioning caused provisioning delays.

Next Steps: – We’re reviewing our provisioning procedures to help prevent this kind of problem from happening again.

Posted in Service Interruption

YA75910 | Service Restored | Users may be unable to search for recently created messages and files. | 8/31/2016 07:15 PM UTC

Final Status: We’ve identified that the infrastructure that facilitates Yammer search had become degraded. We routed traffic to an alternate capacity to resolve search functionality.

User Impact: Users may have been unable to search for recently created messages and files.

Scope of Impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that any messages or files created after 3:30 PM UTC would not have been searchable.

Start Time: Wednesday, August 31, 2016, at 3:30 PM UTC

End Time: Wednesday, August 31, 2016, at 6:55 PM UTC

Preliminary Root Cause: The infrastructure that facilitates Yammer search had become degraded.

Next Steps:
-We’re investigating log data to isolate the underlying cause of the infrastructure degradation.

This is the final update for the event.

Posted in Service Interruption

YA75910 | Service Degradation |Users may be unable to search for recently created messages and files. | 8/31/2016 3:30 PM UTC

Current Status: We’re investigating an issue in which some users may be unable to search for recently created messages and files within the Yammer service. We’re gathering log data to troubleshoot the issue and determine the next steps of the investigation.

User Impact: Users may be unable to search for recently created messages and files.

Scope of Impact: While we’re not aware of any customer reports of impact, our monitoring indicates that any messages or files created after 3:30 PM UTC will not be searchable.

Start Time: Wednesday, August 31, 2016, at 3:30 PM UTC

Next Update by: Wednesday, August 31, 2016, at 8:30 PM UTC

Posted in Service Interruption

YA75841 | Service Restored | Users may have been unable to see their Yammer feeds. | 8/31/2016 12:32 AM UTC

Final Status: We’ve determined that a database issue on a portion of infrastructure that facilitates Yammer feed functionality resulted in users being unable to access their feeds. By design, an automated recovery feature took the appropriate action to restore service health.

User Impact: Users may have been unable to see their Yammer feeds.

Scope of Impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that any user attempting to access their feed may have been impacted.

Start Time: Tuesday, August 30, 2016, at 8:55 PM UTC

End Time: Tuesday, August 30, 2016, at 9:10 PM UTC

This is the final update for the event.

Posted in Service Interruption

YA75682 | Service degradation | Tenant administrators are now able to initiate subscription changes without provisioning delays. Affected tenant administrators may see the subscription stuck in the “Finalizing” status.

Current Status: We’re continuing to monitor the progress of the provisioning backlog, which is now approximately 40% processed.

User Impact: End users are not affected by this issue. Tenant administrators are now able to initiate subscription changes without provisioning delays. We’re continuing to work on the backlog of requests that previously accumulated. Affected tenant administrators may see the subscription stuck in the “Finalizing” status.

Scope of Impact: A few customers have reported this issue, and our analysis indicates that all new tenants will be potentially affected.

Start Time: Wednesday, August 24, 2016, at 10:00 PM UTC

Preliminary Root Cause: A configuration issue within the infrastructure that handles Yammer provisioning is causing provisioning delays.

Next Update by: Wednesday, August 31, 2016, at 2:00 AM UTC

Posted in Uncategorized

YA75739 | False Positive | Admins may experience delays when provisioning new tenants or new subscriptions | 8/29/2016 9:29 PM UTC

Final Status: This issue is a duplicate of incident number YA75682. Please reference YA75682 for the latest status.
Posted in Service Interruption

YA75682 | Service Degradation | End users are not affected by this issue. In earlier stages of the incident, administrators may have experienced delays when provisioning new and existing subscriptions. Currently, tenant administrators may experience delays when provisioning new subscriptions and my see the subscription stuck in the “Finalizing” status. | 8/29/2016 9:51 PM UTC

Current Status: We’ve confirmed that the configuration change has improved new tenant provisioning time. We’re monitoring service health while the provisioning backlog continues to process.

User Impact:  In earlier stages of the incident, administrators may have experienced delays when provisioning new and existing subscriptions. Currently, tenant administrators may experience delays when provisioning new subscriptions and my see the subscription stuck in the “Finalizing” status.  

Scope of Impact: A few customers have reported this issue, and our analysis indicates that all new tenants will be potentially affected.

Start Time: Wednesday, August 24, 2016, at 10:00 PM UTC

Preliminary Root Cause: A configuration issue within the infrastructure that handles Yammer provisioning is causing provisioning delays.

Next Update by: Tuesday, August 30, 2016, at 1:00 AM UTC

Posted in Service Interruption