Hey Lisa,

Thanks for reaching out!

It *looks* like you've already narrowed down what the culprit in your issue is here. From what we can see in the screenshots you've provided, it seems your theory here is correct - you've got some spikes in latency starting at hop #1 (96.55.32.1) that's carrying through your entire route to the final destination.

Changing the WAN IP address *may* help alleviate this issue, but we unfortunately don't have any knowledge of what IP address (or other settings) you'd need to enter here (sorry!). It may be helpful to reach out to whoever manages this WAN to see if they'd be able to be of any assistance with this.

Please let us know if you have any other questions!

Best wishes,

-Gary