Pinging Emmett-PC [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
:awe:
ryan@falcon:~$ traceroute 72.21.81.13
traceroute to 72.21.81.13 (72.21.81.13), 30 hops max, 60 byte packets
1 firewall.loc (10.1.1.1) 0.268 ms 0.328 ms 0.398 ms
2 196-226-gateway.nt.net (209.196.226.1) 10.425 ms 11.403 ms 11.446 ms
3 209NTL226-57-5.nt.net (209.226.57.5) 12.403 ms 13.401 ms 13.398 ms
4 be4.dr01.nrba.on.aliant.net (207.231.227.69) 16.567 ms 17.404 ms 18.384 ms
5 xe-0-3-0.bx01.toro.on.aliant.net (142.166.149.65) 23.400 ms 24.431 ms 24.429 ms
6 be8.bx01.nycm.ny.aliant.net (207.231.227.54) 37.466 ms 36.537 ms 37.456 ms
7 ae4.asbn.va.aliant.net (207.231.227.86) 45.462 ms 32.944 ms 34.937 ms
8 206.126.236.112 (206.126.236.112) 35.953 ms 33.579 ms 34.574 ms
9 72.21.81.13 (72.21.81.13) 34.570 ms 33.747 ms 34.696 ms
ryan@falcon:~$
This is while streaming 1080p off twitch.tv so not really the best example
i pay for 20/5
I read a Wikipedia article a long time ago that said "jitter" is a misnomer, so I've been calling it "packet delay variance" (PDV) ever since.ms is so 1999...
Fast connections are measured in us.
And if you're really close, ps.
Latency measurements are of little use. Jitter is where it's at.
Have high jitter and you may have tons of bandwidth but VOIP and some games will still go bezerk with lots of jitter.
Ping an ip (if on 'doze) be sure to use -t so you get some real time to see replies. Note high and low values. Difference is jitter. Should be less than 10ms. 1ms is excellent. If your connection is overutilized you may see much higher values.