I have had a problem with intermittent ping spikes recently. Essentially every 1-5 minutes I get very brief spike between 2000-3000ms. I had believed it was a game server issue until pinglotter revealed this to be happening across every connection no mater what server i was connected to. It just was not a problem with most games and internet use.

https://share.pingplotter.com/ZuDEgEmbKKv
https://share.pingplotter.com/eSFpfJDpQqQ
https://share.pingplotter.com/byyg1N36yWN
https://share.pingplotter.com/bvdQCD34w33
https://share.pingplotter.com/NYuhTM7Ke35
https://share.pingplotter.com/Vr53TfgYie7

I have tried everything possible as far as I know to fix the issue. Reinstall win10, ethernet drivers, modem factory reset, testing different devices and servers. The game desync/disconnect also coincides with the spike. I have called my ISP and after trying there suggestions they are sending a tech out in a few days. I suppose all I am looking for is confirmation that these pingplotter results do suggest a serious problem with the router/modem so I can press the tech if needed. The second hop is the IP of my in house modem a Cisco DPC3848V. The results are reproducible over the past week and presumably much longer, it just was beneath notice until recently.

My best guess is that this is related to the faulty puma6 chipset and the latency issues that have yet to have a fix patched into the firmware which includes the Cisco DPC3848V, although this issue seems more severe than descriptions of the puma6 problem with latency. My second guess is bad power supply maybe, like power fluctuations from he wall causing the modem to fail. My 3rd guess is that this is simply failing hardware.

Hey there,

Thanks for getting in touch with us!

As far as what I can see on your traces that you've sent, I can't quite gather enough information to tell you for sure where the issue lies. It does look like, on your traces, there is some significant packet loss in intermediate hops, but that packet loss is not carrying to the final destination (which is the hop we really care about), so I'm not *quite* seeing a ton of area for concern (only taking into consideration the screenshots I can see).

I would suggest doing the following: Run the trace to your gaming server for as long as you can, 24x7 if you're able. When you notice an issue with your game, make a note of what time it happened, and head back to PingPlotter when you're ready. The goal here is to correlate PingPlotter results to actual real-world performance. Is there a "problem pattern" near the time of your game failing? If so, you can then trace back to see which device the problem started at. Here's a page we've got on some problem patterns and how to identify them:

https://www.pingplotter.com/fix-your-network/common-network-problems

If you don't see a problem pattern, then you might need to leave PingPlotter running for more time in order to actually find where your problem is. Just keep trying, and when you think you've caught something, that's when you should start investigating who caused it. Here's some information that might help you find this out:

https://www.pingplotter.com/fix-your-network/capture-problem.html

If nothing seems to help, you *may* need to turn to another potential solution; there may be a failing NIC, or an overloaded processor, or maybe a bad graphics card! There are so many variables in gaming that we definitely should look into not only the scope of the network, but also into other equipment that affects gameplay as well.

Let me know if there's anything else I can help with!