Hey Portermelo,

Thanks for getting in touch! It sounds like you've done a lot to try and chase this issue down. Thanks for giving us all that detailed information!

First of all, I can definitely see that you're having some packet loss to Google. It looks like the pattern is originating close to home, and you may not be far off with your "bandwidth saturation" theory!

So, in order to find out truly what’s going on, you'll need to let your trace run for quite some time and investigate the results to be sure. Your goal here is going to be to correlate the issues you're having to PingPlotter patterns. You'll want to start a trace running to the service you're having troubles with, like your gaming server, and leave that running while you're accessing the service. It's important to make sure that you're tracing to the gaming server, because if you trace somewhere else, there's always a different route and that can give you some results that may be inconsistent with what you're experiencing. When you're experiencing that rubberbanding, make a note somewhere of what time it happened, and look back on your PingPlotter data to see if you can find a problem pattern that relates to when the undesired behavior first started.

To start you off on interpreting your results and investigating to full potential, I'd like to point toward a very powerful guide which will be able to guide you through your entire troubleshooting process. That can be found here:

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

If you find yourself in need of some more help along the way after you've implemented what I've recommended above, I'd be glad to offer any further guidance I can. Feel free to head to PingPlotter, hit File -> Export Sample Set, and send the file you've saved to support@pingman.com, as well as some of your notes on what times you experienced the most issues with these games. I'd be glad to take a look and chat a bit more in-depth about the issues you're seeing here!