Hi Rugby,

Thanks for reaching out! I'm sorry this issue been so difficult to pinpoint, but I'm happy to lend a hand.

I can't say for sure using only a screenshot, but there does seem to be a problem starting at hop#1. If this is true, then there may an issue in one area of your LAN.

To be sure though, I'd love to take a closer look at your data. Please share your results by changing your Focus field to reflect 24 hours (or more), clicking File -> Share -> Create Share Page - then, copy/paste the URL of your share page in your reply.

- PingPlotter Sharing

Here are some recommended steps you can take to help narrow the results and find the culprit:

1. Trace to any sites or services you are having issues with (Netflix, Fortnite server, Zoom.com, etc.)
2. You can also trace to your ISP (generally hop #2 or #3). A "WHOIS" google search on the IP address usually provides results about who the IP address is registered to.
3. Trace to your router (Usually the first hop in the route - 192.168.0.1 or something similar).
4. Trace to your NIC (Network Interface Card). In Windows, run Command Line as administrator and type ipconfig and look for the IPv4 address - this is your NIC IP.
5. Finally, trace to your loopback address (127.0.0.1). This lets you verify that any issues you are seeing are not related to the hardware or IP stack on the machine you're using.
6. Trace to a generic reference address like google.com
7. After 24-48 hrs, in your All Targets Summary tab, double-click each entry to bring up their Timeline Graphs.
8. Scroll through the graph (using the slider at the bottom) and when latency or packet loss occurs, compare the graphs and look for where the issue begins.

Tracing directly to intermediate hops (such as your ISP at hop #2 or #3) is important because some devices can down-prioritize ICMP requests where TTL=0 (forwarding the packet, but dropping the response to PingPlotter). This shows up as packet loss, and if many intermediate devices are doing this, it's difficult to tell if it's TRUE packet loss.

Here are a couple of articles which talk about this in a little more detail:

- Interpreting Latency and Packet Loss
- PingPlotter Ports and Packets

Let me know if this leaves you with any questions!

All the best,

Austin Berner
Software Support Technician | Pingman Tools
support@pingman.com | (208) 345-0030