Hey StealthKid!

Sorry it's taken me a week to see your post. I usually try to be speedy, but apparently this was not my week.

I looked at your data again, and purely off of the quantitative data, I see a lot of issues starting at hop 2, repeatedly. Now, this data set is from December, but I do stand by what I said. PingPlotter uses a combination of your plain ol' ping and traceroute to deliver results in a graphical way - so if you just had a ping -t going to your final hop, I'd bet my bank account you'll see the same thing as PingPlotter (except ugly, because... command is ugly. That's why we made PingPlotter to begin with).

If you want to send over some data, you can - but I'd save my breath on that one. If you have a data set that looks like the one sent over in December, it's likely the same issue - and I'd encourage you to compare your patterns to these when talking to the ISP:

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

I'm really sorry that your ISP doubts the software - I'm glad to see that you've still got faith, and I hope we can make a good impression on your ISP here. If you want, you can send over our reviews from customers on Capterra and Spiceworks, along with your data.

https://www.capterra.com/p/143523/PingPlotter/
https://community.spiceworks.com/products/3275-pingman-tools-pingplotter

At this point, it really seems like you've got a grasp on PingPlotter - the struggle now is going to be convincing your ISP that you need some help on your link. Let us know if you need any additional help - but at this point, it looks like you've used it pretty effectively. From one PingPlotter user to another, BRAVO!