ping increased from 17ms to only 30 in a game whilst live streaming and playing 2 4k 60 fps videos and 1080p netflix simultaneously whilst literally 30 minutes ago i was having 200 with just netflix playing.
My ping whilst 2 4k60 youtube videos, streaming at 10k bitrate and playing 1080p netflix.
can you ping this please ipv4:www.google.co.uk it just makes it easier (also the same protocol, ipv6 can give different results) to compare with my reults and others.
Also add the Max column so we can see the actual max spike you get rather than the rigth hand graph, since it's hard to make out.
So this was with a 10k bitrate livestream, 4k 60fps video and 1080p netflix stream. It's still spiking occasionally but its much better than it was before with only 1080p netflix playing.
Interesting, you can see hop 2, which gives a bit more information to this whole thing showing that the ping spikes are actually heppening at that node too, wherever / whatever it is.
Im guessing it's exchange level Routing equipment.
I have several friends who have this exact issue on BT also, I could get some of their pingplotters when they experience spikes and see if there's packet loss at a similar hop.
Yeah im almost certain HOP 3 will give packet loss for everyone. From all the Ping Plotters I've seen there's always 80% ish loss on that hop.
Will be interesting to see if your friends can also see HOP 2. As you can see from my results HOP 2 doesn't respond to ICMP requests so I can never see if the HOP is also spiking.
I've googled the IP of the hop that is having packet loss and there's countless reports about ping spikes, a lot of which are mentioning that IP, seems to be located right in the centre of London so i would assume a lot of connections would go through it.
Ah I see you've mentioned this exact IP before too in another post, so is most likely 100% the root of the issue.
I just remembered I started having this issue back when BT uncapped my bandwidth through DLM. For some odd reason it was capped manually with DLM (not sure how) so when they changed it back it must've changed the configuration to go through that node. very interesting.