said by bluepoint:
You are ignoring the second hop of his tracerts. That's the reason he's having high latency, it's a sign of an oversold node.
Having actually been on a congested "node", I can say that trace route does not look congested. In my case, the "node" was an aggregation router, first IP hop after the DSLAM. The SBC techs referred to it as an, "exhausted router". I saw high latency from that IP hop to the end. OP's trace does not exhibit that characteristic.
What baffles me is that nobody has brought up return path issues. If there is a wide disparity between the forward path (which we can see from the OP's trace) and the return path (which requires a trace from the remote connection back to the OP), that can cause anomalous results.
And if the performance is caused by routing, it may be beyond Road Runner's control.--
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum