View Single Post
Old 25th October 2017, 15:13   #11
Major Dude
dopelabs's Avatar
Join Date: Oct 2006
Location: Silicon Valley
Posts: 531
Send a message via AIM to dopelabs
Originally Posted by sqgl View Post
Someone suggested you use MTR to diagnose your connection and then did it for you. I was just noting that it is hardly worth bothering with because it is deceptive. The French node is not necessarily a bad link in the chain for your stream because there may not be any bad link in your chain (although if there is a bad one then the French one is it).
while it may not give you a definitive answer as to what the issue is, MTR is very much worth running. to start it will show you the general health of the network path your taking. while you may label it as deceptive, if you understand how it works, and how networks work, it is an extremely useful tool as a first step in troubleshooting.

while a lossy node may not represent a problematic node, combined with high latency and/or high deviation chances are thats the culprit... its also very easy to spot if/when your route goes overseas by the obvious jump in latency for said hop and all hops after.

generally the fewer hops the better.... more hops dont always = a worse route, but each additional hop you traverse the greater the chance something can break.

a good example is cogent. cogent is considered 'value' bandwidth which many datacenters and service providers use because of low cost. while 'premium' bandwidth providers such as HE, level3 ,etc cost more, you will generally have a shorter route with less oversubscription.

from philly to san jose over cogent philly pa NY clevland ohio chicago il kansas city mo denver co salt lake city utah san francisco ca san jose ca

from philly to san jose over HE
dopelabs is offline   Reply With Quote