On Mon, 8 Feb 2021 15:31:17 +0000 Mark Rogers mark@more-solutions.co.uk allegedly wrote:
noping is reporting times varying from 11ms to 43ms when run directly on the (OpenWRT on a Pi4) router. --- 8.8.8.8 ping statistics --- 133 packets transmitted, 133 received, 0.00% packet loss, time 2033.1ms RTT[ms]: min = 11, median = 14, p(95) = 23, max = 43
Is that good/bad?
That looks reasonable to me, though the max is a little on the high side. But it does depend where you do the test from - and remember that 8.8.8.8 is not a single fixed destination but is rather a distributed address used in large range of datacentres. Google's DNS servers are anycast systems placed so that they can be as close to as many end systems as possible. This means that /my/ ping to 8.8.8.8 may go to a completely different host to yours. (And because we use different intermediate routers our routes will be very different too).
Here's my result from my desktop (actually it goes over a VPN to a Heztner server in Germany)
--- 8.8.8.8 ping statistics --- 116 packets transmitted, 116 received, 0.00% packet loss, time 3749.2ms RTT[ms]: min = 32, median = 32, p(95) = 33, max = 34
and the same result directly from that VPN endpoint itself.
50 packets transmitted, 50 received, 0.00% packet loss, time 180.9ms RTT[ms]: min = 3, median = 4, p(95) = 4, max = 8
(so there is practically no latency there and the difference is caused by the additional multiple routers between my desktop and the endpoint).
If you are interestred in the latency of traffic to/from a webserver then try httping (which also has a nice ncurses front end.
--- http://www.google.com/ ping statistics --- 45 connects, 45 ok, 0.00% failed, time 46958ms round-trip min/avg/max = 37.8/49.5/65.8 ms
Again, with nothing to compare to I don't know how good/bad that is.
Again, goggle.com is not a single point. A better test would be to a webserver you know is /not/ on a CDN.
For example, my desktop resolves google.com to 216.58.200.14 which gives the following (pretty poor) results
--- http://google.com/ ping statistics --- 32 connects, 32 ok, 0.00% failed, time 51192ms round-trip min/avg/max = 612.7/630.7/907.1 ms
whereas my VM on Hetzner's network resolves google.com to 216.58.212.174 and gives the following (much better) result.
--- http://google.com/ ping statistics --- 50 connects, 50 ok, 0.00% failed, time 50207ms round-trip min/avg/max = 18.6/20.5/45.8 ms
a direct test to 216.58.212.174 from my desktop gives
--- http://216.58.212.174/ ping statistics --- 41 connects, 41 ok, 0.00% failed, time 43651ms round-trip min/avg/max = 75.0/76.8/87.2 ms
which is better than the first test to google.com from my desktop but not as good as the one from my VM.
And a test to google.de from my (Germany based VM) gives
--- http://google.de/ ping statistics --- 33 connects, 33 ok, 0.00% failed, time 33301ms round-trip min/avg/max = 18.5/20.5/29.7 ms
Thanks for the suggestions, I now feel I have more information and no more idea what the problem is :-)
The problem may lie in a number of possible places. You mentioned dropouts on zoom calls. Zoom uses a number of different ports (and both UDP and TCP as transports), see https://support.zoom.us/hc/en-us/articles/202342006-Network-Firewall-Setting... for example. If there are routers beween you and others on the call which prioritise zoom traffic differently you could get dropouts. It is also worth bearing in mind that ICMP is often given a much lower priority than other protocols by most devices so the ping tests you run will only give an /indication/ of possible problem spots.
Some ISPs are better than others too. TalkTalk had a pretty lousy reputation for network congestion at one time. Virginmedia is also known to have had problems in the past.
Ofcom reported on ISPs in 2017/2018 see https://www.ofcom.org.uk/research-and-data/telecoms-research/broadband-resea... which according to BroadbandGenie (https://www.broadbandgenie.co.uk/broadband/help/what-is-broadband-latency reported that EE, plusnet, BT and sky had latency of around 12ms whilst Virgin's was around 20ms - not a huge difference, but if that were coupled with additional problems elsewhere (possibly on your own network) it could become noticeable.
HTH
--------------------------------------------------------------------- Mick Morgan gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312 https://baldric.net/about-trivia ---------------------------------------------------------------------