Sending the data to PingPlotter just moves the data over - it doesn't actually capture the route, which is what your ISP needs.

The discrepancy between MultiPing and PingPlotter is what I'm chasing down here (and the suggestion with going final destination only in PingPlotter). The data you collect that way won't be helpful to your ISP, though. Once we determine the difference between PingPlotter and MultiPing's data (ie: why MultiPing shows packet loss and PingPlotter doesn't), then we can try to get PingPlotter to show the same packet loss that MultiPing does.

A warning here, though. Make sure you're correlating packet loss in MultiPing back to a network disturbance of some kind. The fact that PingPlotter doesn't show packet loss is a warning sign that the packet loss shown in MultiPing might be just because of a router configured to drop certain types of packets - and that the network may be functioning just fine. What symptoms are you seeing?