Traceroutes from a single source are poor tools for positively determining a source of latency. A traceroute only tells a unidirectional story, and an incomplete one at that.
In reality in is essential to use multiple provider/observer based tools to determine point(s) of congestion. However, it is entirely possible to empirically determine who the congested peers are between, which, and when specific geographical connections are overloaded.
In reality in is essential to use multiple provider/observer based tools to determine point(s) of congestion. However, it is entirely possible to empirically determine who the congested peers are between, which, and when specific geographical connections are overloaded.