Hey there Robert,
Thanks for reaching out! I'm happy to share some wisdom about your results here.
Regarding the IP address variance you're seeing, it looks like at certain times (or on certain devices), PingPlotter is tracing over IPv6 or IPv4. The IP addresses you're used to seeing are IPv4, but IPv6 is just as common nowadays. You can read more about these differences
HERE .
For instances where your router is showing high amounts of packet loss, it's not carrying through to the destination (as you've mentioned). This is an example of a router which is down-prioritizing ICMP TTL Expired responses, and is pretty normal.
The most important part here, would be the packet loss we're seeing at
hop #2. As I'm sure you're aware, it looks like it's starting at hop #2 and carrying through to the destination. I'd recommend doing a
WhoIs lookup for the IP at that location and get in touch with the owner (probably your ISP).
It's likely that there's an issue either at hop #2, or perhaps the line leading up to it (maybe the router reboot has something to do with that?).
You can start building a case to present to your ISP in order to help fix this issue, but I'd highly recommend gathering a decent chunk of data first (like 24 hours or more).
Also, feel free to check out our various articles in the Wisdom section of our website - like this one here:
-
Beat Game Lag Like the Pros Lastly, I'd highly recommend checking out
PingPlotter Sidekick. This 'nifty tool was designed for home users and remote workers, and boasts a network troubleshooting suite - straight from their local web server.
Complete with automatic target selection, guided walkthrough, and automated data collection and sharing functionality, this program gives our customers the information they need to fix their network connectivity; either by themselves, or by sharing evidence with their ISP.
If you'd like to know more about PingPlotter Sidekick, you can check it out at:
https://pingplotter.com/sidekick Let me know if this leaves you with any other questions!