The tool is pretty much stable. We don’t see many bugs in the tool. I rate the stability an eight out of ten.

In the 11 years that we've been using it, it's not gone down more than once; and we started with just one help desk on it — we now have five.

I rate the tool's stability an eight out of ten. One challenge with ServiceNow is occasional failures and availability issues, although they are rare. In case of critical operations being impacted, there is no recall available.

The current setup is stable, yet there's a pressing need for continual enhancement in processes and procedures.

I have had no issues with the tool breaking down or bugs. Stability-wise, I rate the solution an eight out of ten.

The solution has not gone down yet.

I rate the solution a nine out of ten for stability.

This is a stable solution. 

It is highly stable solution. 

I rate ServiceNow nine out of 10 for stability. We haven't had any downtime except for platform maintenance and upgrades. 

It is a great product. I haven't had any issues with it so far, and it has been working well.

I have found it to be a stable, reliable solution.

ServiceNow is a very stable product. I have heard a couple of integration issues in some places.

From a perspective of it working, there are bugs occasionally, but for the most part, it is very solid. There are always pockets of problems, but when it comes to Project Management, I am yet to see a significant bug or issue. Most of the bugs and issues are more related to a lack of functionality as opposed to something that is broken or bad data. All such functionalities get added in the next version. 

From the perspective of doing what it is supposed to do, it is very solid. My experience has been very good, especially with the most recent release.

In terms of stability, there may be occasional hiccups, but they are not overly frequent.

We have mostly faced stability issues for the on-premises model. We haven't faced any downtime for the SaaS version.

It is a stable platform.

We don't have any complaints from our customers after they start using the product. Once they adapt to the new look and feel, and the user experience, there's no problem. 

ServiceNow is incredibly stable.

It is proven to be reliable; we have not encountered any issues with it.

The solution is pretty stable. The only thing is that it's a cloud version, and therefore, if your network is slow or non-responsive, then ServiceNow becomes slow and unresponsive. That's a network issue. That is not an application issue.

I think ServiceNow is highly stable. These kinds of tools are used in a big company, and I haven't seen any issues in terms of the core platform. However, if we need to customize something, that would be the point to focus on because this would be something new, not a part of the standard flow for the tool.

We find the product to be very stable. Because it is a cloud-based application, you have your issues with networks and all, but I don't consider that a part of the problem with the application. I find the application to be extremely stable.

From a SaaS perspective, it's very stable. I think in the 12 years that I've been running it, I have seen maybe one or two outages. For the most part, it's pretty stable.

The solution is very stable. We have never had an issue with ServiceNow, I do not remember a time we had a problem with the application. However, there are problems with the network, internet connection, and mobile networks, but not in the application. If there is a connection issue once the connection is established again the recovery is very good because the data automatically start to flow without any problem between both applications.

Azure has had only one incident in three years of use in our experience. 

The product is extremely stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. It has not been problematic at all.

It is a stable solution, and I rate its stability a seven. Although, the troubleshooting functions are complicated to use.

It is totally stable. I never had issues with it.

The stability is pretty good. On average, I don't see many clients complaining about the performance side of stability or availability on the platform.

The stability is very good. We haven't had any problems. It hasn't gone down and it hasn't crashed. There are no bugs or anything like that. I don't see it any now and I haven't in the past - even after 20 or more years. This is flawless software. 

I have not had any issue with the stability.

Very stable so far. I have yet to experience an outage of any of the ServiceNow instances my operations/teams use.

From a user perspective, we noticed a slowdown when we moved from Eureka to Geneva, so I've got a lot business customers that are saying, "Man, your tool got slower." I don't have any stats behind it. It's running all the time.

There are some bugs in the solution.

I rate the solution’s stability an eight out of ten.

The solution is stable. It always works. We haven't had any issues. In this case, no news is good news.

The stability has been good so far. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

I haven't had any issues. As a matter of fact since we've been using it, I can't think of one time where it was unavailable or had an issue. I haven't seen that as an issue from an end user perspective. I have it up periodically. The folks in my unit have it up all the time to monitor the queues and I haven't heard any issues with it.

I rate ServiceNow an eight or nine out of ten for stability.

ServiceNow is a stable solution, and I haven't experienced any downtime with it.

I rate ServiceNow ten out of ten for stability.

It provides good stability. I would rate it eight out of ten.

The solution is stable.

The solution is stable and the performance is good. there aren't bugs or glitches. It doesn't crash. It's reliable. 

This is a stable solution. There's very little that I'm aware of in terms of hiccups and complaints.

It's pretty solid. I think that on our dashboard it says 99.8% availability. Now a lot of my customers in the service desk that do our support line, over the phone or through chat, they're telling me that the CMDB look up for config items on the incoming incidents that they're starting, is way faster in Geneva. They've set it, set it, and reset it. It wasn't just a first impression. It's a lasting, "Thank you. Thank you. Thank you." They sent a special email. We don't normally have people that are raving fans of anything you provide tool wise. We have our customers who are usually raving fans on our airlines. This was kind of surprising to hear.

The solution has excellent stability and we're working with a client that has one of the largest implementations of ITSM and SecOps in the world.

We've had no issues with the stability of the solution.

It is stable. There are no issues at all.

ServiceNow is very stable. The scalability is also great.

It's stable and it's improving. You can't compare ServiceNow with any other tool.

They're always very functional about updates and patching.

The solution is very stable. However, we did have an outage once because their data center was potentially down.

We have had no major issues with stability.

Recently, we've been working with the support because they've been notifying us that there are certain things that may be slowing down our system. Right away, they've advised us that they have that ability to transition us seamlessly and to help us with our connectivity. There are some complaints internally still that we're trying to wade through, but overall we've been quite happy with it. Connectivity for the most part has been very good.

I had no issues. When there is potential for a downtime, they always email me and let me know. Even when I get those emails, I've experienced mild hiccups but beyond that, I've never been locked out for more than maybe 30 seconds in 4 years.

It's been beautiful. We spun the thing up as soon as we signed the contract. Right away they asked us what they names were. We had development tests and production instances. I can't speak to how fast it was bit to was pretty quick. We've not had any system interruptions whatsoever. It's been available 24/7.

We've had a little bit of slowness at times. We're looking into the heart of that and I think that maybe some of that is maybe our implementation. The way we've gone about setting up database calls and things like that. It's hard to say. I can't really speak to that because I'm not working so much with that group. Occasionally, depending on the implementation I've seen it always run smooth and fast.

Other times we have to deal with the internet is right in the middle because it's cloud based. You never know if that's the reason for the lateness. Overall it's a great product.

ServiceNow is relatively stable. I haven't noticed any problems with stability.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

In the last four years, we might have had an outage, but the stability is very good. Since it's cloud-based, we don't see many performance issues.

I love the stability. We were lucky enough to be physically located very close to Service Now. When we were hitting problems with our internal organization to roadblocks, we literally drove up to Service Now headquarters and sat down with them for an eight-hour session to revamp our whole internal process. I was pretty sure that if we would have continued down our own process, we would have taken another six months. However, with Service Now's assistance, we fixed it in one day just by having access directly to Service Now. That was an amazing process. They enabled us to jump forward six months and made things super stable.

Servicenow is a stable product which is an advantage for the business.  As per the current business trends and requirements the expected availability of the products are around 99.9% availability.  hence, we cannot afford the frequent outages 

The stability of the product is good. There aren't bugs or glitches to deal with. It doesn't crash or freeze. It's reliable.

Not in the newer versions. I would say that years ago before ServiceNow really went through a big development of backend data infrastructures and fault tolerance. Today, I haven't really seen any of those types of things.

It's a very new system, and we see bugginess. In Helsinki we found that we were using one feature but we kept getting errors. I thought it was something that I did, so I spent three or four hours and I couldn't get my answers. So then I realized I basically re-realized when I spoke to ServiceNow people and they troubleshooted that it was a bug. In terms of performance it's very good.

We haven't used it in production yet so I can't really answer.

To a degree, yes it's stable, but mostly it's due to data center issues on their side, or it's come down to network issues on our side. Since it's external, it's not internal, you're looking at having to deal with Internet weather, or data center hosted environments, or our instance had the issues, which is pretty rare.

It's been a long time. It's been a very long time. I think mostly they had a roll back of, not a build or an update. It was some type of data change, but I don't recall the details as it was several years ago.

My understanding is that the stability is excellent. 

The stability of the solution is very good.

It's pretty much a stable product.

The stability is really good. As I mentioned earlier, the HR area has a lot of room for improvement in terms of stability. We are trying to customize a lot of things. But overall, in terms of being a stable solution, that is what comes from ServiceNow.

As the tool is SaaS and customization is minimized in the critical early design phase by the Process Workshop's "out-of-the-box" approach, stability and scalability are optimized.

In the time that I've been using it, it's been a pretty great experience.

From what I heard we've had contractors who've come in who've worked on other people's incidences, and they say our incidence is the buggiest of all the other incidences they've dealt with. When we promote update sets some of the updates in the update set don't go to the next environment. It's completely random, and it shows up in the update set in the environment you push it to that it was promoted properly, but it doesn't show up. You have to go into that environment and make the changes. Little things like that, but it's always up and running, unless our company has an internet issue.

The solution is stable. 

In my experience, the solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. I find it to be reliable. 

It is a stable solution.

It is stable. It has been one of the more stable capabilities that we have for operations.

I've never had an issue with it in terms of stability. It's always available when I need it.

I don't really think that we're running into too many stability issues.

The instance is always up and running.

I rate the product's stability a ten out of ten.

This is a stable platform.

The stability is much improved. It's good.

ServiceNow is a stable product.

It is a reliable solution. 

The SaaS platform has been very reliable. ServiceNow has been one of the few SaaS solutions that we have chosen that has not had major issues. The agility to provide test/dev instances, and the seamless access provided by their support team, have been essential in allowing us to work with the solution.

The solution is quite stable. It's actually a big platform with a lot of plugins and a lot of things being introduced in each version. Sometimes there is not enough information about releases. For example, right now we have an issue understanding what the roadmap is for the Scaled Agile Framework.

It's a very stable product, it has a very good SLA and RTO. So far, so good, and I expect it will continue like that.

Stability is assured by the Vendor. No issues found so far.

I think we've got one customer who had an outage once, or maybe twice. One was a mistake we did on an integration and not the fault of ServiceNow. Second one is that the personnel forgot to change some certificates, so the instance was working perfectly, but the customer said, "I have an outage here and why?" We looked at it and we say, "Did you do your work here?" "Oh shit! I have to do it now." Yeah, extremely nice. I never had any issue with ServiceNow.

It's one of the few systems we have in our house that hasn't gone down. It's very stable. As a matter of fact, we don't even put it on our availability list because it's up.

The stability is excellent. There are no bugs or glitches and it doesn't crash or freeze. I find it to be reliable. 

The stability of ServiceNow is excellent. I've never had any issues around its stability, scalability, availability, or any of those metrics.

There were performance issues, minor ones, with one customer. The rest is working really good.

There was an outage at the ServiceNow data center servers, especially on the eastern site. I don't know about all the other data centers, but our data center recently had an outage for at least 15 minutes. Two weeks later we found out about it through some other call, not to the engineer and it was not notified anywhere on the system. I thought ServiceNow would have send out an e-mail or put something on the page saying that the ServiceNow in the data center is out.

Best in class. It has been really good; it's availability, reliability, performance. Sometimes people do dumb stuff with scripts. The performance is not the platform's problem, the problem is with peoples scripts.

The first real latency issue we had was about a month ago. We attributed it to probably some updates that we had run. We backed those off to see if they impacted any of that performance. We were thinking it was something we had done. Come to find out that they had transferred us from their Virginia data site to their San Jose, I believe and they had some issues. Once we recognized that it wasn't on our end, we notified them and they were quick to respond to it. That's the only real latency issue that we've had. It's always a concern. That's something that we're always very aware of is because our users are like, "If ServiceNow continues to grow, what's going to be the impact to performance?"

The platform is developed specifically for IT service management and offers a range of enhanced features. I would rate it seven out of ten.

This is a really stable solution.

It seems to be very solid. We have not run into any errors or problems, although we're not a very heavy user. If somebody was processing thousands of tickets a day, maybe they would run into something, but for us, it's solid. There are no issues at all.

ServiceNow is such a complex piece of software. It's trying to be everything. The way I look at it, sooner or later, it's going to fail, because it's trying to do a lot of stuff. I can't say what or where, but it will. We've seen it a lot of times already with other products. You can't be everything, and that's what they're trying to do.

We've never really had too many issues and anything we have had has been self-inflicted, so it's not ServiceNow's fault.

I haven't had any problems. No latency. No issues.

We have had some issues over time. I think at times, they've ramped us up or given us more processing power. A few times we've had outages lately here too. Sometimes it does seem slow. We've kind of learned not to bring up a list with a thousand items in it. Sometimes there's something that you run that you expect to get a response in a couple seconds and the counter counts up to 45 seconds before you get your response back, so there's certainly some issues. We've seen a few bugs, but no show stoppers.

ServiceNow is a stable platform.

It is stable.

There are no issues with stability that I know of.

On a scale of one to 10, I would rate stability as a seven.

Too early to tell, but not that I'm aware of. That part is not really my area, but I haven't heard of any.

The only thing I can come up with is the fact that we ordered an instance with domain separation or activated that wasn't there from the scratch. We had to raise an incidence and to get it resolved and stuff. You know that it takes you one or two weeks and then everything is done and then it's passed to you.

We do our maintenance updates about once a month but we haven't really had any downtime at all since we've put it in place. We recently went through an upgrade about a month ago, a couple of months ago, and there was no issue, there were no issues at all.

They wanted a ticket to where the customer would see a general global ticket and not have to go through and see if it was an incident or a general request or whatever. And this one particular ticket and the way they have it set up is fairly complicated. They didn't use global tables that should have been used, they customized it and now we are having issues. So we are going to try to get it back to where it is a more simple thing and this should make it more stable.

Every clone release has been pretty seamless. We had one issue with one patch, but that was due to IE issues. It wasn't compatible before IE9 and some of our users were still on IE8, though they weren't supposed to be.

I find it to be very stable.

This tool is stable. It performs well, but like I mentioned, its response time can be improved, but overall, it's good. It's reliable.

The stability is great. There are no bugs or glitches. It doesn't crash or freeze. 

It is quite a stable solution. In the last couple of years we probably had around one or two outages and only one major outage. So it's very stable.

None.

Perhaps we only had one issue that I can remember that we had a downtime, but other than that it's been very stable and very consistent.

It doesn't crash. They have a terrific up time, but I would expect that when you have four redundancies, that goes without saying. I would say that for the things that I like to do, which is muck around in the underlying, I would say that it's going downhill.

The most recently released Geneva locked up a bunch of stuff. A good example is UI16. There's a bunch of stuff that's undocumented and it's locked away. It makes it very hard to get to. I would say that's a definite negative.

We have the occasional problems with slowness, but I can't remember a single instance where it's been completely down.

We haven't had any issues. Of all the systems in our environment, ours has been the most stable. We're up all the time, so as long as our network stays up, our customers have access. We haven't had any issues or complaints about our performance or up-time.

Honestly, I've been extremely impressed, especially as time has gone on. I was on the platform before the high availability came around, and so I want to say it was Knowledge 12. I was actually working for a company on the IT operations desk using ServiceNow. I was in the middle of a session and got called out because ServiceNow went down, and even before high availability, we had a backup pretty quickly. I was able to go break back into my session and get back to it, so now, with high availability, I can't recall a moment since where I have actually seen an instance truly down where the instance itself was down.

There have been problems with applications, but even then, we've hot-patched on the fly to fix issues. It's just so agile at getting back to operational.

With those of whom I have spoken to as ServiceNow admins or those who manage ServiceNow for the company, they've found it relatively easy just to manage it and from a stability perspective and from a scalability perspective I think it's stood up really well.

Stability is a complete non-issue. It is all cloud based and I have never experienced down time with ServiceNow.

The solution is stable. There aren't bugs or glitches. It doesn't crash or freeze.

Sometimes the CMDB, BK table gets slow, however, almost all of the other things are good, at least.

The solution has good stability.

The stability is good and has been improving over the years. 

It is very stable.

It's a stable product.

No.

We've never had it go down or connect. Most times people say ServiceNow is down, it's because our network isn't available, so it's typically not us. You can flip the WiFi on your phone and say, "Okay, that's not ServiceNow." It's been really good.

It's been constantly stable. I wouldn't say never any down time, but I would say that we're usually at four nines.

It's small issues. Not a big impact for production instances and for the current work.

There are issues sometimes. With the updates, we have a line of code that is probably not compatible with that update so we have to go back and see what line of code needs to be edited so that it works with the new update.

I think that's one of the key things with that tool is all of those considerations and problems go away.

It is stable. It seems good.

No issues.

Everything that we've had has been stable. We haven't had really any issues or anything.

No downtime that I know of.

We've had no issues with the performance.

It was never bad, but in the early days there was definitely more outages, and we had an SLA. I think initially we even got some money back from them in the early early days in Progress. I'd say over the past five years or so that the reliability's been excellent.

Rock solid. We have a dev instance where only a couple of us work in development of a few things and ideas. Then in our production instance we do not yet have a mid-server or anything implemented. We're about to, but we are integrated with Centrify for some of the sign-on. From our support desk folks, it's been solid for them. Everybody gets what they needs. It's one of the things in our organization that always works.

We've only had network issues, and we've never had any latency issues. It's always just if the network is down is our only problem. We have had bugginess, but we're going to get too technical for me. It's part of the integration between ServiceNow and Genesis and IVR. There were some issues but they were very technical in nature.

We have. We implemented some various complex ACLs and they've impacted our performance significantly, and we've had several incidents open to help with performance, and it's been kind of a struggle to get the ServiceNow support group to say "Yup, I see it's a problem, let's do this." Eventually they say "Oh yeah, it is." They've upgraded our incidence, they've added indexes to certain tables and things like that, it's just been a struggle, two to three months of constant back and forth to get our performance and our production instance the way that we want it.

It's been very stable.

Over the two years that we've had ServiceNow up and running, we've had a couple of service interruptions. Other than that, no. Some kind of network problem they were having, they had to fall back into a different data center, and that took about 15 minutes, I wish it was a little bit seamless, but we've had a couple of glitches.

No issues encountered.

No issues encountered.

You need to know how to use it. You need to do a scope application. If you have everything on the same table, it gets slow. You need to know how the product works, and you need to adhere to the rules. Otherwise, it would become slow.

I would say in terms of stability, it is 90% stable. There are certain things which I've experienced with my other customers. So I was not happy with that. So that's the reason why I'm putting a 90% for the stability.

I haven't found many stability issues in this tool. The uptime is relatively good.

It has. With the new update in Geneva, there's a few snags with the presence, but they're getting that ironed out. As far as up-time goes, it's always been available.

We have had no performance issues.

There have been no issues with the stability.

It strongly depends on customer awareness of ServiceNow best practices. In some cases stability is an issue.

No issues encountered.

Stability is assured by the vendor. No issues found so far.

There's been very little downtime in the year we've had it. I think we've had one outage that was five minutes or so.

We did have some performance issues where some of the system areas were slow, but that was really our fault. It was a blip in the lifecycle. I mean comparatively we don't have any downtimes, we've got a hundred percent availability, so we're very happy in that regard. I'm also very happy with their support, they're very engaging and they've been very helpful when we have had problems.

The solution is stable.

It is very stable. We have only had five minutes of downtime in three years. 

The availability has been great. Any issues we've come up with we've been able to easily rectify with working with support, so I would say it's definitely great.

We encountered no issues with stability.

It is very stable.

For the most part, the product is very stable. We host customers ourselves and we know how difficult it is. As a host provider you're not completely 100% in control of everything, you're dependent on other vendors to be up.

No, their support staff helps out by monitoring the instance and recommending action. We have some slowness from time to time but it usually due to issues on our ent.

In 12 years, I've rarely seen a failure of their cloud hosting, if ever. It's incredibly stable. 

There are other questions then about performance, however. Sometimes it runs slowly in the cloud due to the number of transactions you're placing on it. That said, it doesn't fall over. It isn't compromised by a security breach. I'd give it 99 out of 100 for stability.

This solution seems stable.

I have found the solution to be stable.

It is very stable.

Currently it's stable.

The product has very nice stability. We haven't had any reliability issues. There aren't bugs or glitches. It doesn't crash or freeze. It works quite well.

Stability-wise, this product is very good.

No. Very stable.

There have been issues because of our customer as they wanted an on-premise installation. It's different than cloud solution. Stability is not a problem now. If there was a problem, then it was an infrastructure problem, not a problem of ServiceNow.

It is really good. There is no downtime.

The performance also depends on if you have too many changes, depends on the script and the developer that has worked on that instance. In the out of the box service, no, I haven't had any performance issues.

It's a stable solution.

I would say yes. Sometime some delay of latency but otherwise it is very stable.

The solution could improve by being more stable.

It is quite stable from the implementation perspective.

We've not experienced any downtime whatsoever.

There were no issues with the stability.

There were a couple of issues on ServiceNow side which were promptly addressed by ServiceNow support.

We are a B2B business and we have a large clientele. 

Our clients are large enterprise companies, and with the number of agency items that we have to enter into ServiceNow, it can handle it easily.

It is a stable product.