Hey Marka,

Thanks for reaching out!

In regards to your first question, PingPlotter is coded for a maximum export of 500k samples when using the trace export.

With that said with the data you have provided this does a pretty good job of demonstrating that your network issues are starting at your ISP (hop 2). You can confidently conclude that this is an ISP issue because the packet loss/latency that occurs at the final hop in your traces is also present at hop 2 (and the hops in between) while your local network (hop 1) stays clear of any sign of an issue.

Considering this I suggest next checking out the following article we have posted about building a case with your ISP:

https://www.pingplotter.com/fix-your-network/build-a-case.html

This should be helpful in preparing to reach out to your ISP with this data you have collected and shared this far. With that said if this leaves you with any other questions or concerns please let us know!

Thanks,
-TJ