Thanks for writing in - and thanks for sending over such detailed info on your issue!
From what we can see in the results you provided, and your description, this really *appears* to be a possible bandwidth saturation issue (https://www.pingplotter.com/fix-your-network/common-network-problems/#bandwidthsat
). While your router may not show any bandwidth usage during problem periods - it’s possible for bandwidth saturation to happen *outside* your network (at one of the ISP owned hops), which your router wouldn’t be able to see.
In the first pp2 file you’ve provided here, there’s a pretty clear pattern happening at the final destination (during the hours you mention) where the latency increases (and gets a bit “jagged”), and there’s an increase in packet loss. It’s a bit tough to see, but this pattern *does* seem to start at hop #3 (if you zoom out to a 12 hour view, you can see a pretty clear pattern of latency through the packet loss - which continues through through the entire route). This would imply that the issue is originating somewhere between hop #2 and #3.
Bandwidth saturation can have a number of symptoms, including packet loss. If a device is receiving more requests than it can service, it may start dropping packets, which could result in patterns like the one you’re seeing here. The fact that the issue is happening consistently between 7p and 11p - which would likely be the busiest times for the network - would be another strong indication of bandwidth saturation.
We’ve got an article that goes over some tips for dealing with bandwidth saturation (including some guidance on what to do if it’s possibly on your ISP’s end), which may be of some help to you here:https://www.pingplotter.com/wisdom/article/bandwidth-saturation.html
Hopefully this helps get you headed in the right direction. If you have any other questions, just let us know!