Found this:
https://forums.cox.com/discussions/internet/slow-trace-route-wtime-outs/149845
Found this:
https://forums.cox.com/discussions/internet/slow-trace-route-wtime-outs/149845
What you're seeing there looks more like ICMP de-prioritization and not really packet loss. If packet loss was occurring, you'd see it all the way through to the destination. If you think about it for a moment, how is it possible to reach your destination without packet loss if you're traffic is going through a hop that is dropping packets?
While I don't disagree with you about this issue, I think there was something weird going on with Cox routing in general. If you read the post OP referenced you will see latency spikes that follow through to the destination. ae2.rd.la.cox.net more specifically, which looks similar to ae0.rd.ch.cox.net but I am not familiar with Cox's naming scheme. I think it is semi resolved now. If OP still has the problem, I suggest using Pingplotter and changing the traffic type to either TCP or UDP and see if the "issue" still occurs.
