Btw: Network Latency is measure using PING of the target domain.name or IP address.
Ping is a one time attempt performed three times- try this first.
To get a good picture of the path to a resource, use PATHPING (name or ip) and it will take ~200 seconds or more - - WAIT for it. You will see the delay at each node, loss at each node and even the losses between notes.
As an example, here's my results to Techspot.com:
Code:
Tracing route to techspot.com [50.22.252.218]
over a maximum of 30 hops:
0 jeffPC7 [192.168.0.5]
1 localRouter [192.168.0.1]
2 gateway-system [xx.yy.zz.zzz]
3 tge7-7.wlvgcabn-cer02.socal.rr.com [76.166.19.217]
4 tge0-8-0-10.vnnycajz-ccr01.socal.rr.com [72.129.13.100]
5 72.129.13.0
6 ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
7 ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
.
16 techspot04.techspot.com [50.22.252.218]
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 jeffPC7 [192.168.0.5]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% localRouter [192.168.0.1]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% gateway-system [xx.yy.zz.zzz]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% tge7-7.wlvgcabn-cer02.socal.rr.com [76.166.19.217]
0/ 100 = 0% |
4 18ms 0/ 100 = 0% 0/ 100 = 0% tge0-8-0-10.vnnycajz-ccr01.socal.rr.com [72.129.13.100]
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% 72.129.13.0
0/ 100 = 0% |
6 19ms 0/ 100 = 0% 0/ 100 = 0% ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
0/ 100 = 0% |
0/ 100 = 0% |
0/ 100 = 0% |
16 80ms 0/ 100 = 0% 0/ 100 = 0% techspot04.techspot.com [50.22.252.218]
Trace complete.