Hello,

There's definitely no doubt that you're likely lagging pretty hard - your PingPlotter results *do* show some bandwidth saturation at your final destination.

Hop #3 may simply be down prioritizing ICMP TTL expired packets (which is why when you're tracing to Google, you get a latency spike at hop #3 that doesn't carry on to hop #4). We suggested that you trace directly to the 3rd hop to see if the behavior changed when you were targeting it directly. If the picture looks the same when doing that, then that device may simply be set to down prioritize *all* ICMP requests. The pattern of bandwidth saturation that's affecting your final destination *does* seem to start at hop #3, though (the pattern there just amplified when compared to your final target).

Hop #3 is *most likely* where your issue is beginning. Your goal at this point should be to get a clear picture of this so that you can reach out to the appropriate party (possibly your ISP) to reach a solution. The guide I mentioned in my last post (http://www.pingplotter.com/netnirvana/) has some great tools for building a compelling case to bring to your provider.

If you should find yourself with any other questions, please let us know!

Best wishes,

-Gary