4 ms·
Heck, even I write mails to my ISP and tell them which interconnect points they're having issues at which a simple traceroute/mtr show me. And I mostly get posi
by noselasd 12y ago
Heck, even I write mails to my ISP and tell them which interconnect points they're having issues at which a simple traceroute/mtr show me. And I mostly get positive feedback.
With a bit more sophisticated tools, you'll get more confidence. Or if you're Netflix, I'd assume you can just call up level3, ask them to resolve the transit issues you're having with Verizon, and get feedback and reports about it being verizon not upgrading their interconnect to level3. I'd not be terribly surprised if verizon is one of the 6 peers mentioned at http://blog.level3.com/global-connectivity/observations-internet-middleman/ http://blog.level3.com/global-connectivity/observations-inte...
- zero_intp 12y agoTraceroutes 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.