Thanks for getting in touch - and thank you for trying out PingPlotter!
There are a few things that stood out in the results that you've provided here: first being that there are some patterns of latency occurring at hop #1 (some mild "spikes") that seem to be carrying through your entire route. There's also some packet loss occurring at hop #2 that seems to be continuing through the rest of your route. Both of these occurrences imply that something pretty "close to home" may be causing you issues (something between the machine running PingPlotter, and hop #2).
We're assuming this trace was preformed with the network switch you mentioned plugged in - is that correct? If so, does removing the switch and plugging your computer directly into your modem produce better results in PingPlotter (it sounds like it does, but we just want to be sure).
If bypassing the switch and connecting directly to the modem produces better results (and a better experience with your network), the switch itself *may* be the culprit here. At this point, it'd be worthwhile to test this theory a bit further (run some tests with the switch plugged in, and removed - and compare results) to see if you can further prove (or disprove) this theory.
We've got a great guide that goes over using PingPlotter to locate (and solve) network issues like this one, which may prove helpful to you here:https://www.pingman.com/network-nirvana/
If you should find yourself with any questions, or needing any further guidance - please don't hesitate to reach out!