Hi Jon,

Thanks for getting in touch with us! I'm happy to offer some wisdom here.

You've definitely captured a problem here, which seems to be starting at hop #2 (which looks to be your ISP gateway). However, hop #1 is down-prioritizing ICMP TTL Expired packets (which doesn't affect your connection) which is sort-of masking any results on your local network.

To ensure the problem isn't local, I'd recommend tracing to 192.168.1.1 for a period of time to ensure the spikes don't start at your router (and you can use this data to convince your ISP the issue is not on your end).

Here's an article which outlines some great information about bringing a case to your ISP:

https://www.pingplotter.com/fix-your-network/build-a-case.html

As with a lot of Tier 1 support, you may need to be that "squeaky wheel" for a bit in order for them to address the problem seriously

If on the other hand the problem is local, I'd recommend using PingPlotter to troubleshoot your NIC (Network Interface Card) as well as your loopback address (IP Stack and hardware):

- In Windows, run Command Line as administrator and type **ipconfig** and look for the IPv4 address; this is your NIC IP.

- Trace to your loopback address (127.0.0.1).

I hope that helps! Please let us know if there's anything else you'd like a hand with.