We have about 800 schools and we use Statseeker to monitor the WAN router at each site. Up/down (uptime and downtime) is our biggest thing. After that, we use it for monitoring bandwidth, interface utilization and different things like that. We use it for all the statistics it can provide in real-time and for historical usage. We use those statistics to plan if there is a need for upgrades — things like that.

Statseeker provides the basic monitoring status of our network elements, including latency, ping delays, and ping drops. Its strengths lie in a couple of areas. Firstly, it is not an expensive tool. Secondly, it can retain data for up to around two years.

Our primary use case for this solution is network alerting.

We primarily use this solution for polling and interface utilization. 

We use it for bandwidth monitoring and email alerts when there are significant events like interfaces or devices that are down. Those are our big use cases.

Our primary use of Statseeker is for our interface. In our data center, we are typically a Cisco shop. We can now look thirty days into the future based on past stats of trends or fashion. 

If we have 10 servers in the field office, we can jump up to twenty based on utilization. We have the evidence. It is a lot of manual work to create those reports, but a bit easier now.

We use it for network monitoring, mainly for our core in-campus devices. 

Our primary use case for this solution is network monitoring.

Our primary use case for this solution is fault management.

We use Statseeker to monitor all the devices on our network. This includes:

• the network switches
• our gateways to the cloud
• our kiosks that are mounted throughout our building
• any other device we deem to be important

We want to know exactly when they go down.

We use this solution to control bandwidth congestion, and also for the recovery of unused data network ports.

Our primary use for this solution is network monitoring.

Our main use of Statseeker is for verifying traffic after several upgrades or failures.

Our primary use of Statseeker is for monitoring and the utilization of our network devices. We initially got Statseeker because we needed more visibility and better historical data.

We primarily use this solution for monitoring. We use the Mac version.

Our investment in this solution was customer-driven. When we have a request from a client business we look at what we have. If we cannot satisfy the request then we look into investments such as this.

Our primary use case for Statseeker is for network monitoring.

Our primary use for this solution is to watch and record ports for the entire network.

Interface monitoring, mainly for interface statistics. We use it for monitoring up/down, capacity management, bandwidth utilization, reporting.

Our primary use case is for polling and interface utilization. The solution helped us to monitor our network availability. Now we're more alert to what's going on. 

Our primary use for this solution is historical traffic wrapping.

This solution only handles a very small slice of what we actually need to monitor, so it is just another product in a set of products we use.

I was primarily using this solution for network traffic analysis. We are switching to another product.

We use this solution for monitoring the status of all network devices.

We monitor links, bandwidth utilization, and device CPU and memory utilization. We generate reports of the top ten utilization links, which are helpful for acting proactively.

• Monitoring entire network
• Creating outage and performance reports

Our primary use case is for monitoring traffic.

Our primary and only use for this product is for network monitoring.

Capacity management of devices and carriage services.

Our primary use for this solution was to monitor devices. I was the Statseeker administrator before we switched to a new solution. I do, however, still go back and use it.

Our primary use for this solution is troubleshooting. We use it for logging and monitoring the routers and switches in the environment. It assists us with capacity planning.

The primary use of Statseeker is to monitor network performance on physical, data, and network layers of the network.

We primarily use this solution for monitoring. We check primarily for failures or latency in the network. 

We primarily use this solution for educational content.