I have been using www.pingtest.net to check my internet connection recently but I am never able to test packet loss
Why not just ping via IP or URL with the built in PING function of Windows for packet loss detection?
Like if I want to check for packet loss to google I will just
ping www.google.com -t
and CTRL+C when i want it to end to get the results from the persistent pinging.
Ping statistics for 216.58.217.100:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 43ms, Average = 28ms
Control-C
^C
C:\>
With use of traceroute you can even find which hop is having troubles vs assuming the issue is with the server at the other end. I have used this to point out issues with Comcasts backbone and make a phone call to them and surprise them as to how i found the issue once I get a hold of someone who has a clue as to what i am talking about. They had a backbone that was sketchy and nasty latency but with multiple backbones it was a roulette as to when you would hit the problem. Once traceroute found the troubled backbone I had its IP to hit it with pings and report it as a problem to them.
C:\>tracert www.google.com
Tracing route to www.google.com [216.58.217.100]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BlackBox [192.168.150.1]
2 9 ms 13 ms 9 ms 96.120.70.1
3 10 ms 8 ms 8 ms 68.87.181.217
4 10 ms 9 ms 9 ms te-5-1-ur02.woburn.ma.boston.comcast.net [68.87.
145.182]
5 9 ms 11 ms 11 ms 162.151.113.98
6 20 ms 26 ms 19 ms be-70-ar01.needham.ma.boston.comcast.net [68.85.
69.177]
7 22 ms 25 ms 25 ms be-7015-cr02.newyork.ny.ibone.comcast.net [68.86
.90.217]
8 22 ms 20 ms 24 ms hu-0-11-0-5-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.87.58]
9 52 ms 53 ms 52 ms as27589-2.miami.fl.ibone.comcast.net [75.149.228
.186]
10 45 ms 46 ms 49 ms 216.239.62.125
11 24 ms 22 ms 21 ms 72.14.237.134
12 29 ms 31 ms 29 ms 216.58.215.53
13 28 ms 27 ms 29 ms 209.85.143.113
14 41 ms 42 ms 31 ms 209.85.143.255
15 26 ms 27 ms 28 ms iad23s42-in-f4.1e100.net [216.58.217.100]
Trace complete.
C:\>