PRTG Network Monitor Freeware
Paessler GmbHExternal reviews
214 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Fast, Flexible Monitoring with Powerful Auto-Discovery and Alerting
What do you like best about the product?
What I like most about PRTG is how quickly I could get meaningful monitoring without spending weeks in configuration. The auto-discovery actually worked well in our environment, and the sensor-based approach made it easy to monitor very specific things (like one service on a VM instead of the entire server).The remote probes are very helpful for segregated networks. I also like that it doesn’t feel overly complicated compared to some enterprise monitoring tools.The alerting system is flexible — I configured escalation rules so night alerts go to only one on-call engineer instead of the entire team.
What do you dislike about the product?
The licensing model based on sensors can get confusing when your environment grows. In the beginning it felt affordable, but once we started monitoring more granular metrics, we hit the sensor limit faster than expected.Also, when monitoring across multiple remote sites, troubleshooting probe disconnections sometimes takes longer than it should.
What problems is the product solving and how is that benefiting you?
Before PRTG, we were mostly reactive — users told us when something was down. Now we get alerts before the helpdesk phone even rings. It helped us identify a bandwidth bottleneck caused by nightly backups overlapping with office hours.This allowed preventive maintenance instead of emergency shutdowns. Downtime incidents reduced noticeably, and production managers now trust IT more because we prevent problems instead of reacting to them.
Auto-Discovery That Actually Works—Deep Hardware Health via SNMP
What do you like best about the product?
When I drop a new core switch or a hypervisor onto the network, PRTG’s "Auto-discovery" finds about 90% of what I need (CPU, traffic, disk) without me having to manually look up OIDs or hunt for templates. It’s the "lazy man’s" dream that makes me look like I’m working much harder than I am.
What do you dislike about the product?
Paessler counts every single metric as a sensor. Want to monitor one switch? That’s not 1 license; that’s 20 (one for ping, one for CPU, one for every active port). You hit your license limit way faster than you’d expect, which forces you to be stingy about what you monitor.
What problems is the product solving and how is that benefiting you?
We used to have constant finger-pointing between the app devs and the net-ops team. By setting up a PRTG dashboard in the main office, I can prove in 5 seconds that the latency is at the database level, not the switch. It’s saved us countless hours of "ghost-chasing."
PRTG Easy to Implement and Use
What do you like best about the product?
We implemented Paessler PRTG in our production network to monitor our core and edge infrastructure, including Juniper MX routers, QFX switches, server infrastructure, and WAN circuits. We are using a mix of SNMP, NetFlow, and custom sensors to monitor interface utilization, BGP/OSPF status, CPU/memory, temperature, power supplies, and environmental sensors in our MDF/IDF locations.
Deployment was straightforward on a Windows Server VM, and adding devices via auto-discovery significantly reduced setup time. We’ve also built custom sensors for specific use cases, which has been very flexible. Updates have been smooth with no downtime issues, and the mobile app allows our team to receive alerts and acknowledge incidents while on call.
We did have one issue polling a Juniper MX router via SNMP due to configuration specifics, but Paessler support responded quickly, reviewed our logs, and helped us adjust the configuration so polling worked correctly. Overall, support has been responsive and knowledgeable.
Deployment was straightforward on a Windows Server VM, and adding devices via auto-discovery significantly reduced setup time. We’ve also built custom sensors for specific use cases, which has been very flexible. Updates have been smooth with no downtime issues, and the mobile app allows our team to receive alerts and acknowledge incidents while on call.
We did have one issue polling a Juniper MX router via SNMP due to configuration specifics, but Paessler support responded quickly, reviewed our logs, and helped us adjust the configuration so polling worked correctly. Overall, support has been responsive and knowledgeable.
What do you dislike about the product?
There are no major complaints. As our environment grows, sensor count management and licensing tiers require some planning to ensure we stay within limits. However, this is more of a scaling consideration than a product issue.
What problems is the product solving and how is that benefiting you?
PRTG provides centralized visibility into all aspects of our network infrastructure, including core routing, switching, WAN links, and critical services. Before implementing PRTG, troubleshooting often required logging into individual devices to diagnose issues. Now we receive proactive alerts for link degradation, device resource thresholds, and routing adjacency changes.
This has reduced mean time to detect (MTTD) and mean time to resolve (MTTR), improved uptime, and given management better reporting on bandwidth utilization and system health. It has become a key operational tool for maintaining network reliability and performance across our organization.
This has reduced mean time to detect (MTTD) and mean time to resolve (MTTR), improved uptime, and given management better reporting on bandwidth utilization and system health. It has become a key operational tool for maintaining network reliability and performance across our organization.
PRTG Delivers Fast, Script-Free Monitoring Visibility
What do you like best about the product?
What I genuinely like about PRTG is how fast it goes from zero to useful. Within a couple of hours of installation, we had visibility into our VMware hosts, core switches, Windows servers, and even SSL expiry monitoring without writing any custom scripts.
The auto-discovery feature is surprisingly practical. It’s not perfect, but it gives a solid starting baseline. Also, the sensor-based model makes you think in terms of "what exactly do I want to monitor?" rather than just adding machines blindly.
The auto-discovery feature is surprisingly practical. It’s not perfect, but it gives a solid starting baseline. Also, the sensor-based model makes you think in terms of "what exactly do I want to monitor?" rather than just adding machines blindly.
What do you dislike about the product?
Sensor licensing can get confusing as environments grow. You start small, but once you begin monitoring disk, CPU, services, processes, ports, and custom checks — sensors increase rapidly.
Also, advanced customization sometimes feels Windows-centric. If you're heavily Linux/cloud-native, you will rely more on SSH sensors and custom scripts.
Also, advanced customization sometimes feels Windows-centric. If you're heavily Linux/cloud-native, you will rely more on SSH sensors and custom scripts.
What problems is the product solving and how is that benefiting you?
We caught disk saturation issues before they caused outages.
We identified high CPU patterns during nightly batch jobs.
SSL certificate expiration alerts saved us twice from production outages.
We identified high CPU patterns during nightly batch jobs.
SSL certificate expiration alerts saved us twice from production outages.
PRTG Needs Major Improvements Despite a Great Map View
What do you like best about the product?
PRTG's map view is a game-changer. I can drag-and-drop my switches, servers and loT devices onto a floor-plan and instantly see health at a glance. It saves me 10-15 min every morning compared to logging into each box."
What do you dislike about the product?
"The notification flood during a spike can be overwhelming. Even with thresholds tuned, PRTG still sends a bunch of alerts for minor dips that don't need action. I end up muting a few channels just to keep sane
What problems is the product solving and how is that benefiting you?
Before PRTG, we were blind to bandwidth hogs on our office Wi-Fi. After deploying it, we pinpointed a rogue video-streaming app that was choking the network. Result: 30 % boost in employee productivity and lower ISP costs thanks to traffic shaping."
Sensor Factory Makes Complex SLAs Easy with a Clear Green/Red Health Metric
What do you like best about the product?
The "Sensor Factory" sensor is the secret sauce that nobody talks about. Most people just use the default SNMP or WMI sensors, but when you have a complex SLA where you need to show "Application Health" based on five different variables (e.g., a mix of Ping, SQL query response, and a specific Windows Service status), the Sensor Factory lets you write custom boolean logic to create a single "Success/Fail" metric. It turns a cluttered dashboard into a clean "Green/Red" light for management
What do you dislike about the product?
The "Ajax GUI" feels like a time capsule from 2012. While it’s functional, the way it handles "Libraries" and "Maps" is unnecessarily clunky. If you want to move a group of 50 sensors to a different probe, you can’t just drag-and-drop them in a modern, snappy way; you often end up clicking through nested menus that feel sluggish once your sensor count crosses the 5,000 mark.
What problems is the product solving and how is that benefiting you?
The "Finger-Pointing" Fix: We had a recurring issue where the DB team blamed the Network team for slow queries. By deploying a Remote Probe inside the DMZ and using a "Packet Sniffer" sensor specifically for TDS (SQL) traffic, I proved that the latency was happening at the application layer, not the wire. It saved us about 10 hours of weekly "war room" meetings.
A True Swiss Army Knife for Packet Sniffing and NetFlow
What do you like best about the product?
The Packet Sniffing and NetFlow capabilities are surprisingly robust for an "all-in-one" tool. While most people just use ICMP pings, I love that I can set up a sensor to look for specific high-latency headers or rogue protocols without needing a separate, dedicated analyzer. It’s the "Swiss Army Knife" that actually has a sharp blade.
What do you dislike about the product?
The "Sensor-based" licensing is a psychological trap. You think you have 1,000 sensors, but then you realize a single core switch consumes 48 sensors just for basic port monitoring. It forces you into a "monitoring diet" where you’re constantly deleting sensors to save room, which is the opposite of what a monitoring tool should encourage.
What problems is the product solving and how is that benefiting you?
We had a recurring "ghost" slowdown every Tuesday at 2 PM. Standard tools showed high CPU, but PRTG’s Top Talkers feature identified an automated, unauthorized cloud backup from a single workstation that wasn't on our inventory. It saved us from a $20k unnecessary bandwidth upgrade.
PRTG Makes Monitoring Easy with Clean, Intuitive Dashboards
What do you like best about the product?
PRTG is extremely easy to set up compared to other monitoring tools I’ve used. Auto-discovery works well, and the sensor-based model makes it simple to start monitoring without complex configurations. The UI is clean and dashboards are intuitive even for non-technical stakeholders.
What do you dislike about the product?
Licensing based on sensors can become confusing and expensive as the environment grows. Also, some advanced customizations require deeper technical knowledge than expected.
What problems is the product solving and how is that benefiting you?
PRTG helped us centralize monitoring for servers, switches, and applications. We now detect outages and performance issues early, which reduced downtime and improved response time for incidents.
PRTG’s Auto-Discovery and Granular Sensors Make Network Monitoring a Breeze
What do you like best about the product?
The way PRTG auto-discovers devices actually mirrors real network topology better than most tools I’ve used. It picked up oddball OT devices on our VLANs that even our CMDB missed.
Sensor granularity is practical — I can monitor one noisy interface without creating alert storms for the whole switch.
The web UI loads fast even over VPN. That matters when you’re troubleshooting from home during an incident.
Sensor granularity is practical — I can monitor one noisy interface without creating alert storms for the whole switch.
The web UI loads fast even over VPN. That matters when you’re troubleshooting from home during an incident.
What do you dislike about the product?
Historical data retention tuning feels unintuitive. I had to experiment a lot to balance storage vs detail.
Cluster/failover setup works, but it’s more Windows-ops heavy than expected for a monitoring tool.
Licensing based on sensor count sometimes pushes you to combine metrics in less-clean ways.
Cluster/failover setup works, but it’s more Windows-ops heavy than expected for a monitoring tool.
Licensing based on sensor count sometimes pushes you to combine metrics in less-clean ways.
What problems is the product solving and how is that benefiting you?
We caught intermittent fiber degradation months before failure because PRTG showed slow optical power drift trends.
Reduced “false blame” between network and server teams — device-level visibility ended arguments quickly.
Helpdesk escalations dropped because we now alert on saturation before users notice.
Reduced “false blame” between network and server teams — device-level visibility ended arguments quickly.
Helpdesk escalations dropped because we now alert on saturation before users notice.
Sensor-Based Licensing and Auto-Discovery Make Monitoring Easy to Justify
What do you like best about the product?
The sensor-based licensing actually helped me justify monitoring to management. I could show exactly what each sensor was doing instead of paying for vague “device counts.”
The auto-discovery worked surprisingly well in our mixed environment (VMware + physical switches + a few legacy servers). It didn’t just detect devices — it suggested useful default sensors.
I really appreciate the custom dashboards. I built a live NOC screen in under an hour without touching any complicated scripting.
Notifications are flexible. I was able to set up different alert thresholds for business hours vs after-hours without complex rule logic.
The auto-discovery worked surprisingly well in our mixed environment (VMware + physical switches + a few legacy servers). It didn’t just detect devices — it suggested useful default sensors.
I really appreciate the custom dashboards. I built a live NOC screen in under an hour without touching any complicated scripting.
Notifications are flexible. I was able to set up different alert thresholds for business hours vs after-hours without complex rule logic.
What do you dislike about the product?
When you scale beyond a few thousand sensors, you really start paying attention to probe performance tuning. It’s not “set and forget” at larger scale.
The UI, while functional, still feels slightly dated compared to newer SaaS monitoring tools.
Some advanced configuration settings are buried in menus that aren’t very intuitive.
The UI, while functional, still feels slightly dated compared to newer SaaS monitoring tools.
Some advanced configuration settings are buried in menus that aren’t very intuitive.
What problems is the product solving and how is that benefiting you?
We had intermittent WAN drops between two branch offices that weren’t being logged clearly. By creating custom QoS sensors, I could prove packet loss was happening upstream of our firewall — which saved us weeks of back-and-forth with our ISP.
It gave our small IT team visibility similar to what larger enterprises have, without hiring a dedicated monitoring engineer.
Reduced our average incident diagnosis time from “hours of guessing” to “15–20 minutes of checking historical graphs.”
It gave our small IT team visibility similar to what larger enterprises have, without hiring a dedicated monitoring engineer.
Reduced our average incident diagnosis time from “hours of guessing” to “15–20 minutes of checking historical graphs.”
showing 1 - 10