Hello, so I've been having issues with my wifi and been using PingPlotter to try and get to the bottom of it. Firstly I tried using Google DNS as a target, and every single hop is going haywire with packet loss (This happens with pretty much any target). [PingPlotter1]


More interestingly, I started 3 different targets with all of them connecting to my router, with all 3 of them showing completely different results, 1 with very slight occasional packet loss, 1 with no packet loss whatsoever and one going haywire with packet loss, although all of them were connected to my router and running concurrently. [PingPlotter2-4]

I am at a complete loss and have no idea how to even infer these results so any clarification would be appreciated, thank you.

Hi Xiztenzzz,

Thanks for posting those screenshots!

You might be just overloading your router with pings and so it's throwing away the majority of them and not responding (packet loss). I recommend you start with just a single target to your router and see if that changes things.

If you do see packet loss with that single target, then your most likely looking at an issue with your Wifi. Try plugging in an Ethernet cable to see if that improves the connection. If not, then you may need to swap out your router.

Let me know how it goes!

Okay,

So i just did a single target for the router and came back with no packet loss.

So what could be the explanation for the Google DNS trace, as there was packet loss on every single hop?

I think in your Google DNS trace your router was "de-prioritizing" the expired ICMP packets PingPlotter was sending it. It's not an uncommon thing for intermediate hops to do this. You can read more about this here.

What you should take from this is that your home network appears to be ok. The next thing to test would be your ISP's network. You can do this by starting a trace to hop 2 of the Google DNS trace (90.247.64.1). If you see issues here, you're likely dealing with an issue int heir network.