While no solution is perfect, Pico Corvil Analytics is highly stable and effective.

I rate the stability of Pico Corvil Analytics a nine out of ten.

It's pretty stable. We have never had any issues or any side effects from Corvil being on the network.

The only times we've had issues is when certain sessions that needed investigation were not monitored to begin with. We had to manually add them and then wait for the issue to recur. But overall, as far as the device itself is concerned, we have had absolutely no issues.

It's very stable. It just runs continuously. We get hard drive failure alerts every now and then. We had one instance where we got a group of them all at once, but they handled it pretty well. Out of the entire time I've been working with them over the last decade, I've had one server fail.

The stability is pretty impressive. I have heard that the newest offering of the server is even more awesome. We don't have the newest server yet. Our servers are pretty old, as in a few years old.

We have a couple of flows that are taking a little hit, meaning there is so much traffic coming in that the servers drop packets. But again, that's an old server. We've already spoken to Corvil about it and Corvil has said the solution would be to limit the amount of traffic or get the newest servers that they have. Those have bigger capacity, bigger hard disks, bigger memory, etc.

But the other business offering that we use Corvil for, which I personally support, has no problem at all. There are no dropped packets, it's completely reliable. I wrote what we call our "end of day" process. It takes the data from Corvil and the data from our process and tries to reconcile them, to see if all the data that my bosses get is actually in Corvil. It always comes out 100 percent clean, which means all data is being captured. So the reliability is very high.

We've had no problems at all with its stability. We haven't had a failure, we haven't had to replace one, there's no disk failures or anything like that. You'd think a box like this, with disks constantly in use, that they would be the first things to go. That's been fine.

We did have one issue with a decoder causing the whole capture daemon to crash and restart. That was fixed pretty quickly by Corvil. We said to them, "We keep getting these errors," and they took a look at it and said, "Yeah, it's the decoder." They were able to reproduce it in the lab. We gave them a sample of the data and by the next month - they do monthly Decoder Pack updates - they fixed it. You can tell when that happens because you see in the Decoder Pack release notes "such and such decoder: Improved the robustness of the decoder." That invariably means it was crashing the appliance. That was the only reliability issue we've had but luckily that was specific to one decoder.

The stability has been good. We haven't many updates on the same platform that we are on (9.2). It has been pretty stable. There hasn't been any type of outages.

The stability has been good. We have not had any major outages.

Corvil is pretty stable. We just have too much data going into the boxes. Because of that, it requires more maintenance than average.

We have one person in the USA and one person in Europe maintaining about 90 devices. The product is high maintenance. We have a lot of sessions, more than Corvil's overload. So, we get packet drops, high CPU rates, and disk drive discards.