Thanks for the follow up, and the additional .pp2 file!

The data you've got here looks to tell the same story as your first file: hop #3 still isn't a great responder, but what we *can* see there implies that it may be involved in your issue.

The pattern at hop #3 does indeed seem to change up when you experience issues between 3:20-3:24am (as you noted). There's also another instance at 3:40am where your final destination shows a small bump in latency. During this instance, hop #3 actually reports back some latency (instead of packet loss), and the pattern there matches up with the hop(s) directly after it. Based on this, we can infer that your issue is most likely occurring *somewhere* between hops #1 and #3.

Your next steps should be to isolate any variables (that you have control over) to see if you can definitively narrow down what the source of your problem is. If you're tracing over a wireless connection, try moving to a wired connection to see if that has any impact on your results. Another step may be to disconnect anything in your network that is actively using a network connection, and then start plugging things back in (one at a time) to see you can identify anything that may be contributing to your problem (and be sure to do this while still tracing with PingPlotter, so you can see any changes in your patterns!).

The guide that Pete referenced in his initial response (https://www.pingplotter.com/netnirvana) covers some other best practices and strategies around this idea, and may come in helpful here as well.

Hopefully this helps out! If you should find yourself with any questions, or needing any other guidance - please don't hesitate to let us know.

Best wishes,

-Gary