The packet loss here is much better than it was in the first picture you posted. You can say with some certainty, though, that this problem is between your computer and hop 1 (or possibly at hop 1). It looks (based on latency) like hop 1 is actually inside your cable provider.

Since you eliminated most of the possible culprits from your network, then you start to have to look pretty strongly at the cable provider as the problem. This could be your cable modem, or it could be anything between your cable modem and the device at hop 1. There is probably a lot of infrastructure here owned by the cable company, and the problem probably exists there someplace.

I think you need to continue pushing at your cable provider to solve this problem for you.

The packet loss you're seeing isn't too bad, though, and it could be dismissed by some as not a problem. If possible, I'd recommend that you continue to run PingPlotter continuously, and look and see if evening weekday hours get worse. This is a classic time for cable connections to have problems. The most compelling kind of evidence is time-of-day based, where you get > 2% packet loss during the worst times (7pm to 10pm, weekdays, usually).

Keep track of where you experience problems in whatever application you're using. It's very important, when complaining of problems, to not just have PingPlotter results. You need to be having problems with something that uses your bandwidth - a VoIP connection, gaming, stock streaming, video streaming (or something similar). Keep track of problems you have and note them in PingPlotter. Then, when you create graphs of problems, you have real-world problems correlated with PingPlotter data, which is hard to refute.

- Pete