When mtping receives a response, it displays the time between when the request was sent and when that response was received. It also includes a count of how many times the request was repeated. For example:
host-16: mtping dataexpedition.com ACT_IDSTR dataexpedition.com (220.127.116.11:8080) Response 0 of 214 bytes after 0 repeats in 63ms (Version 2/0): servedat - 1.17.3 May 2016 - DEI, DOC-2.1.5 MTP-osx-4.2.3 1875 00000001: ExpeDat-1.17D Data Expedition Inc., DataExpedition.com Server Statistics (11703): Name: servedat Version: 1.17.3 Platform: osx Clock: Wed Aug 17 10:24:26 2016 Clock Skew: 0 seconds Load: Current: 0, MaxConfig: 1, MaxStart: 1, TotalStart: 7 Capacity: Limit: 10, Exceeded: 0 Up Time: 1.15 weeks Config Time: 1.15 weeks Idle Time: 1.07 days Errors: Errors: 0, Failures: 0, Warnings: 0, Denials: 0
The above output indicates a latency of 63 milliseconds.
To continuously monitor latency, use the "-c" option to specify multiple requests:
host-17: mtping -c 3 DataExpedition.com:8080 ACT_PING dataexpedition.com (18.104.22.168:8080) 0 bytes from 22.214.171.124: count=0 repeats=0 time=60 ms 0 bytes from 126.96.36.199: count=1 repeats=0 time=17 ms 0 bytes from 188.8.131.52: count=2 repeats=0 time=15 ms 0 bytes from 184.108.40.206: count=3 repeats=0 time=17 ms --- dataexpedition.com mtping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 15/27.250/60 ms
Latency versus Round Trip Time
The latency measured by mtping may be significantly higher than the network round-trip-time due to the following factors:
For a more accurate assessment of latency, continuously monitor over a significant period of time. Also see Tech Note 0021 for a detailed discussion of factors affecting latency, loss, and speed.