Ping is not really a good way to measure packet loss. Many modern IT infrastructure products these days will deprioritise responding to ICMP echos when it's busy - some permanently.... and you probably won't know which. There's also going to be a big void between you and what you're testing against that you won't have much visibility of. That said, MTR is a tool that will provide some visibility into that route and will continually ping test against all the IP hops en route to give you an indication of response times and packet loss......but it's using 'ping' as the measure. MTR will continually test all those hops until you tell it to stop. Here's what it looks like

Other ways to test are polling service ports. For example you could TCP ping on port 80. Websites are usually going to prioritise responding there for obvious reasons. For 8.8.8.8, you could perform name lookups polls. Not a low level network test for sure but another way you can test real world response times and latency. Uptime Kuma is an entry level tool that will do that for free. Here's what it looks like

There are a lot more tools out there of course but no one wants to read a War & Peace post

Agreed - makes sense. Thx!

That’s certainly good news. I mentioned this thread to customer support who said they escalated internally. I hope they are paying attention to what’s been discussed and everyone’s experience.

From a technology perspective, sheet happens and I'm less fussed about the actual technical problem and more about how they failed to managed customer communication and expectations.

That's what they need to learn from this.

Edited by nofappingway (Thu 11-May-23 15:09:50)

V sad to see the 2pm issue (latency spikes and increased loss) is back....

It peaked at 1.5% here. A lot better than previously, but certainly still should be 0

Bad enough to kill Teams video call quality... Perhaps as much the jitter....

https://imgur.com/a/d8ejv58

Hmmm, I see it too. Throughput (which I care more about) is unaffected though thankfully.

TCP 80 ping to BBC
ICMP ping to 8.8.8.8

At approx 3pm, it settles and returns to normal as it did before.

I will update my ticket with this information and I suggest others do the same.......but it's so much better than it was the past 2 weeks.

Edited by nofappingway (Thu 11-May-23 15:35:54)

In reply to a post by Henry8:

Bad enough to kill Teams video call quality... Perhaps as much the jitter....

https://imgur.com/a/d8ejv58

I find it odd that your minimum latency decreases shortly before you see increased latency.

Edited by nofappingway (Thu 11-May-23 15:34:59)

Others dont see the same?

My guess is the route to BQM was optimised at about 13.10.
Then we have the usual 2-3pm silliness kick in...