Despite lacking some advanced features, I can confirm that Spiceworks is a stable solution.

It's quite stable and reliable. There are no bugs or glitches. 

I've never experienced the website being down.

I have never faced any downtime. When we increased the inventory, the tool became very slow. So, we increased the RAM, and it was automatically fixed.

It's stable. It's well developed and the maintenance is pretty simple aside from having to go in and take out old devices. But you don't really have to mess with it to keep it running. Every once in a while something will glitch up. I just have to restart it and it works fine. This only happens maybe once every six months. 

Usually, if I have to restart it, it's because the server that's hosting it has shut down and it didn't restart correctly or something like that. The servers reboot periodically, so sometimes it doesn't come back up cleanly or whatever and I restart it. But for the most part, it's pretty maintenance-free when it comes to glitches and stuff.

Spiceworks is stable, but I think more work needs to be done to make it more stable and globally accepted so it can compete with solutions like SolarWinds.

I have not had any issues with stability.

Overall, the stability is fairly decent. It's pretty good. I've got some reservations about how any resource you click on goes out to the Cloud. I could also do with the UI advertising being a little less. I've inadvertently clicked on several of the ads thinking it was going to show me some value-added feature within Spiceworks and I get bounced off to some other place, but that's not what I want. And I am a bit emotionally triggered and pissed off because of it because it's wasting my time and it's not what I want.

The solution is very stable.

Stability has been solid for all the years I have used this product.

The solution is very stable. It's reliable and efficient.

We haven't had any issues with the stability.

There were no issues encountered with the stability.

The stability of the program is remarkably good, with some exceptions. As I've noted, any installation in excess of 2500 nodes is going to be slow and it requires some extra work to maintain and configure. If you don't do it right, the application will perform poorly and crash. Similarly, there are plug-ins that you can add (written by IT pros) which may decrease reliability. Overall, however, I think it's very good. I wouldn't say perfect; my test install fails about twice a week and requires a service restart.

I encountered with stability problems, but I suspect that it was a local server issue.

We have not encountered any problems.

I almost never experienced problems.

There was no issue with the stability.

The server would become sluggish as more assets were populated in the system.

No issues encountered.

Spiceworks is stable for our purposes.

We have no issues with the stability.

The stability is excellent, but it can be affected by poorly written 3rd party add-ins, so beware.

As our database grew in size, so did the frequency we had to restart the application on the server. Spiceworks had a memory leak that would eventually bog down the server it was on and force us to restart the service, which would take about 45 to 60+ minutes. Obviously these restarts never came at optimal times. By the time we were getting ready to retire Spiceworks, we were restarting the service twice a month.

No issues encountered.

It regularly fails when we're upgrading.

I think we did have some trouble, but it was not really the fault of Spiceworks. It was more the way that we reconfigured our firewalls and ports, so it couldn't discover the many things. And with all this stuff going on with ransomware and stuff like that, it's going to be challenging for all of those companies to be able to browse a network, including your network equipment, but not allowing any ports open. It's kind of difficult.

Stability has been a problem only a few times but barely a blip.

Only issue was with scalability. After some time, as the back-end DB grew bigger, the solution started to perform slower. In the end we even had to reset the DB and archive the old one so it could run smoothly again.

No, none whatsoever.

The stability is lacking. We have to restart the software about one two too times a week.

Yes, too many. We tried it on a VM, but we had to reboot every 2 days. We migrated it on a real server, new installation, etc., but despite the fact that the server resources are really over-scaled (8GB ram, disk 15,000 rpm, etc.), we still have problems, slowness, stability, crashes, etc. The only positive is that we do not have to reboot every 2 days. It's sometimes 2 weeks before we have a problem.

There were issues with the stability.

There have been no issues with its stability.

I don’t know the technical details, but I know that stability became a huge issue after about eight months especially as we began to become more sophisticated in how we used the system.

No issues encountered.

Regarding the network scanning you might find it will slow down network performance but with correct schedules this was resolved.

No issues encountered. It runs in minimal resources.

No issues yet.