For the most part, it's relatively stable. However, there are some times where it seems like it runs a little slow and you have to reset things to get it back going again. My other comment is on NetFlow is a lot of times in order to pick up new devices, I have to do a restart on the respective NetFlow collecting server. 

I do the deployment and maintenance of this solution.

If you rank from one to 10, I would give it a nine for stability. It is a really stable tool.

nGeniusONE increased our application and network uptime. nGeniusONE is pretty quick and stable. Whenever the Internet goes down, it will automatically alert us. Then, the team will immediately work on fixing it with the service provider, like CenturyLink. The network uptime has increase by 20 to 30 percent.

There is a 10 member team dedicated to maintenance of the solution.

Stability-wise, I rate the solution a ten out of ten.

It's very stable. We've never had any problems with it.

I am satisfied with the performance of nGeniusONE.

It's very stable. It's very rare that there are any issues that are attributable to the NETSCOUT product.

From a stability perspective, we have not had any issues. We haven't had it break or go down.

I haven't necessarily encountered issues from the stability perspective, but I certainly find it inconsistent in the way it drives reports. For example, if you follow the standard procedure to monitor size or to monitor bandwidth, you're going to find that for about 30 percent of them you will have to do some level of tweaking and customization to make it work. It seems to either have a number of bugs in the tool that we have been reporting and they have been fixing as they go, or it's just part of the functionality that we have to do things differently for a lot of sites. It's not stability, it's more from a standardization perspective. I think that they would do better if they simplified the rollout process.

The product is very good. We have very few problems. And if we do have any issues,  NETSCOUT gives us very good support. They have the right engineers that know the issues. And if anything is wrong with a device, you get an RMA. 

So far, the stability has been good. There have been a few issues, mainly because we haven't been using it long. I've been having to catch up and upgrade and bring it from the floor up, so hopefully it will become a great tool.

I rate the stability a six or seven out of ten. The product crashed a few times within six months of implementation.

The stability is okay.

NETSCOUT nGeniusONE is stable. 

The solution is great. It's a solid rock.

For the most part, it's pretty stable. We've had some instances where we've had to have boxes restarted, probes restarted. But overall, the performance has really held up.

It is reliable.

nGeniusONE is very stable. We have very few problems with it.

We haven't had any issues with it going down or not working. The server that we're using is our own server and we have their software loaded onto it. All the issues that we've had have been our actual server. We had to replace our server once because it died on us. But as far as the software and the actual NETSCOUT appliances that we have going to the nGeniusONE go, like the Packet Flow Switch, etc., we haven't had any issues with them since I've been here, which is three years and counting. It hasn't had any downtime that was not scheduled.

NETSCOUT nGeniusONE is very stable.

It's very stable. Every once in a great while we'll have to reboot the nGeniusONE server. That may be server-related and not application related.

The stability is good. We haven't had a major failure for years. Apart from the hardware's age, the software is pretty robust.

It's 100 percent stable.

It's very stable. 

When we first got the tool, there were some performance issues. Eventually, they worked out the issues through various upgrades and server hardware enhancements. That was a plus.

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

NETSCOUT nGeniusONE is stable.

The stability could be a bit better. We are working right now to find solutions to improve the stability and we are in discussions with NETSCOUT about that.

The stability is excellent.

The solution is pretty stable.

We haven't had any problems with stability.

The stability has been pretty good. I haven't had any issues with the hardware, for the most part. It's a little tricky working with if you don't go through NETSCOUT for the packet flow switching. Right now, we use Gigamon, which we've had some older iterations of and some issues with. But as far as the hardware from NETSCOUT goes, we've had no issues.

Overall, it seems to function really well. We've only had one issue, but that was due to a power outage. It seems to perform well in a virtualized environment and I don't have anything bad to say about the stability.

Stability is a tricky question. It is stable, but the way we use it, we have a lot of tweaks and a lot of specific and detailed configurations on the InfiniStream. It's a very manual process to configure it right now. We're also looking into ways to automate that and, hopefully, eliminate the human error.

So it's stable, but once you start doing more and more with it, there is always something happening in the background that we're not sure of, that fails or something happens, and we have to troubleshoot it and understand it.

Other than those bugs I mentioned, we haven't encountered any issues with stability. The system has been rock solid. It's just stable.

In general, the stability is good, but we have had one or two incidents where specialized support was required.

It is a very stable product, if it's properly implemented. Anybody who is using the product should probably use Professional Services to implement it properly.

The stability is mostly good. However, we just had an outage.

We see it overload once in a while. It doesn't have built-in protection. Therefore, once it gets too much data, it tends to crash. Then, we have to recover it.

The stability is good, so far. We are probably five nines up.

Stability, for us, has been an issue but, to some degree, I think that's from a standpoint of capacity. People are wanting more from the system than what we originally deployed it for, so it's pushed it to its limit. As a result, we're deploying additional capacity.

The stability is only fair. It goes down a lot.

The stability of this product is ok.

Stability-wise, the platform works fine.

We have a lot of timeouts when we are trying to assemble data packets together or trying to pull down a view of one particular call. However, overall, it performs adequately.

Currently we're running quite stable. There were a few hiccups in the beginning with stuff not working. But currently we're running more or less stable. We are running on version 6.2.2. There are a few useful things in 6.3, but we were advised not to go that route yet because it's not 100 percent stable. Our sales engineer said to hold on, just to see how some of their other clients experience it and see how many issues are still being noted in the system before we move over to that newer version.

The stability is very good. We have had no issues.