The solution has performed perfectly for us. The Google search powered engine has always been extremely quick to return results. We've always found it to be very reliable and it's a good fit.

It is 80% stable. Some users face issues in Chrome and Firefox. So, we sometimes have to be involved with the users to check.

We have faced some stability issues, which were fixed by the actual service team pretty quickly. I rate the stability a seven out of ten. 

The stability is pretty solid. We've never had major outages or any workflow issues that weren't caused by an administrative error. It's been pretty stable as far as a ticketing platform is concerned.

We've had no issues with stability or downtime at all.

The tool is stable.

The stability of the solution is quite good. We don't have crashes. It doesn't freeze. there aren't bugs or glitches. It's reliable.

I didn't see any real issues with it. I was there for about nine months, and I might have seen two outages in that time. I also didn't see any performance issues coming through on that.

The tool is highly stable; we've never had any outages or downtime. Freshworks employs a continuous delivery method with Freshservice, so new releases and updates are integrated seamlessly as they are released. There is no impact on the end-users or the agents, so the solution is very stable.

Freshservice's stability is good - it'll take whatever you throw at it.

The solution is stable. 

The uptime is fantastic. We very rarely have any issues with anything going down. Sometimes, it randomly slips into Arabic, which is weird, but it only happens to one user. So, I don't know what the user is doing. After refresh, it goes away. It might be a user problem.

The product is stable as it has not crashed.

It is a stable solution. My company hasn't faced any problems with the solution.

The solution is in the cloud and very stable. there are no bugs or glitches. 

The solution is stable and reliable. There are no bugs or glitches. We can look at the reports to see if there are any services that have been delayed and get to the reason why. Everything is very clear. 

The only hiccups I've seen are due to having integrated with Okta. We've run into some problems with the Okta integration, but that's because they're different systems, and whenever you're dealing with APIs trying to manage the connection between services, you do run into issues.

I haven't heard of issues with bugs or glitches. It's my understanding that it is stable and reliable.

Freshservice is stable.

Freshservice's stability is good.

We haven't had any issues with the stability of Freshservice. However, we have had some issues with data imports, we have noticed that large amounts of data can get stuck. This is something that we haven't seen in other solutions. 

I understand since this is a solution for a different segment in the market, it should work well because you don't have to import a huge amount of data. You usually have to work with small to medium-sized chunks of data and there should be no problem. However, if you're trying to import a huge amount of data, it's is going to get stuck.

It is stable. It doesn't have any outage or governance issues.

It's been stable and we've had no issues with instability.

Freshservice has been highly stable.

We've had no issues with stability.

We haven't seen many problems. I'm on a list to be notified of any service outages. It happens maybe once a year, so Freshservice is stable. 

The stability is good and just as it should be. We haven't had any issues with instability.