We switched out whole-knowledge search to an “and” instead of “or” search. We have 10,000 examples. But this made it unstable and it timed out in the middle of searches. Now we have just one URL that supports people use and another for the general masses.

We had numerous outages due to issues with product and data center issues.

Good stability – partially because we implemented it well for hundreds of concurrent users (not thousands) and we never have issues.

I haven't noticed anything because it's browser-based. I haven't noticed any kind of dramatic instability beside the fact that our environment isn't fully rolled out with Chrome. We are a Microsoft environment, so working with Internet Explorer could have its latency, but it's not the tools, it's more of what our devices are and what our infrastructure is.

Stability is fantastic. I never have any problems.

We have been seeing a little bit of latency here and there, but we haven't been able to identify it. We are still in the process of trouble shooting it, seeing if it's something with the network or with the services of the product.

The solution is fairly stable, regardless of the version clients use. The serious challenge the solution faces, however, is that CA is not investing in the service management suite.

Historically, we have had issues, but recently it has worked very well and now we have no complaints.

Yes, once or twice the agents would stop working to provide the information required.

We encountered no issues with stability.

No issues.

It has been stable. We haven't had any issues with instability.

No.

Yes, sometime it takes a long time to update the newest status of ticket.