Health Edge said:
I also notice it looks like your on a Cox Business connection using a static IP?
No, it's a home connection. That DNS entry you highlighted just means that's one of the routers in the path between my system and the destination. There are two routers between me and the one you highlighted.
Although your comment gave me a good idea. I remotely connected to my work PC and performed a tracert to 68.12.14.34. Here are the results:
Tracing route to 68.12.14.34 over a maximum of 30 hops
1 7 ms <1 ms <1 ms 192.168.0.1
2 29 ms 23 ms 23 ms 10.8.0.1
3 33 ms 27 ms 23 ms COX-68-12-10-22-static.coxinet.net [68.12.10.22]
4 36 ms 31 ms 22 ms COX-68-12-10-82-static.coxinet.net [68.12.10.82]
5 34 ms 30 ms 33 ms ge-1-0-5.101-jun04.mtc3.okc.ok.cox.net [68.12.8.9]
6 91 ms 414 ms 135 ms 68.12.14.34
Trace complete.
Since the tracert shows latency on the same IP while taking a different path, I have to rule out my earlier theory that the problem resides with 10.0.128.1. Either there is some congestion at the two routers I tried to ping or the latency that I observe is just a function of the way those specific routers work. At this point, there is not enough data available for me to determine which is correct. I've got quite a bit of evidence of slow speed, but not enough data to pinpoint exactly where the problem is.