It's very stable. It can go up to a year or two without a reboot. It mainly gets rebooted when I do an upgrade.

During 2015 there were a couple of releases and I had a few stability issues. That was mostly because I moved the database from a Windows appliance to the Linux back-end. It didn't quite sync across. I just deleted the maps and rebuilt them from scratch and that fixed all the problems. That was the only real stability issue we've had across the journey.

We had one upgrade that didn't go as well as it could have, but Anna was able to jump on it with our support engineer and fix it within 15 minutes. It was just a matter of reaching out. They were on the phone within 20 to 30 minutes and got it sorted for us.

Plixer Scrutinizer is a very stable solution.

It's one of the most stable platforms I've worked with.

Plixer Scrutinizer has very good stability. It's been around a long time and its networking visibility tool is fantastic, so it's extremely, extremely, solid.

I would describe Plixer Scrutinizer as a solution offering a medium stability level.

It is extremely stable. I don't ever play with it. I have never had to tweak or tune it. We have had to upgrade it in the past when they have made a major architecture change. Other than that, we sort of forget that the box is running, use the GUI, and go. It does what it does. It doesn't crash.

One person is required for maintenance and deployment. There is a backup guy, but all he does is look at my docs and repeats what I do. He doesn't spend any time on it because I don't spend any time on it. If it were to crash right now and had to rebuild it, we would just download a new one and start over because that is how infrequently we touch the product. So, no one probably remembers the database passwords anymore because in six years we haven't had to touch it.

We didn't experience any bugs.

I haven't had any stability issues with it at all. I haven't seen it flake out or experienced database issues.

I'm the only person who maintains and upgrades it.

The stability is pretty good. We like it.

It is quite stable. We did just encounter a very strange device (a network scanner) which sends us so many flows that the device almost crashed the server of Plixer. However, this is exceptional. We just discovered this issue about a one week ago. Otherwise, Plixer is very steady and has worked very well. We usually never encounter an issue. It is great. 

Because we use the main dashboard for maps to understand the use of the link and present it on the big screen TV, sometimes we are obliged to reset the browser everyday in order to refresh it. We had some little bugs because of this, but we don't know yet if this is coming from Mozilla Firefox, the browser, etc. Otherwise, it is very good.

In terms of stability, it was good, but I wouldn't say that it was excellent.

I have seen a few crashes, however, it's very rare. While it is stable, there is always room for improvement. But it's fairly stable, and in the user experience, it remains consistent.

It's rock-solid. 

It sits there and it runs solidly. There are multiple people in there every day doing some sort of report-generation or review. We don't have any plan to expand usage.

We're happy with it. The solution is stable.

We have one person who is required for deployment and maintenance. Their role is network administrator.

On a scale from zero to 10, the stability is about an eight. From time to time, we have some issues that need to be fixed by their support. Usually, the support fixes the issues quite quickly. I would say it is between good and very good, in that range.

There is one person (the head of the network group) who maintains the server right now. There is also a backup if they are not available. We have a few people who are able to do some configurations on the system.

It's very stable. We have not had a problem with it.