What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

up time and request status and why they are different?



Report for Ping 269
Report Time Span:	4/10/2012 12:00:00 AM - 4/10/2012 11:59:00 PM
Sensor Type:	Ping (30 s Interval)
Probe, Group, Device:	Local probe > Internet Sites > Basemine Maintenance BT 2
Uptime Stats:Up:	95.64 % 	[22h55m46s]	Down:	4.36 % 	[1h2m43s]
Request Stats:Good:	94 % 	[2705]	Failed:	6 % 	[177]
Average (Ping Time):	594 msec

networking prtg-network-monitor-8-x snmp

Created on Apr 11, 2012 7:41:23 PM

Last change on Apr 12, 2012 9:56:23 AM by  Torsten Lindner [Paessler Support]

1 Reply




uptime means the uptime of course. For requests it's slightly different, because PRTG only accounts downtime between at least two consecutive failed scans. So if only one request fails, it's accounted as failed/bad request but does not effect uptime. If a scan fails, the sensor goes down. To be exact, with most sensors after a failed scan PRTG performs an immediate re-scan and if these both fail, the sensor goes into down state. But that gives no exact measurement for downtime, PRTG can't know how long the target is already down. So it takes at least one more scan following the scanning interval for PRTG to have a proper valid statement for downtime.

best regards.

Created on Apr 12, 2012 9:56:43 AM by  Torsten Lindner [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.