title: How is it possible for traceroute to timeout, yet the site will load fine in a browser?
body: <p>I am able to load www.cnn.com in Chrome, yet when I do a traceroute from the command line (OSX), it times out at level3.net</p>
  
  <p>I used this Chrome extension to verify the IP that Chrome is using for www.cnn.com 
  (I can't find a way with Chrome debugger to view IP addresses):
  <a href="https://chrome.google.com/webstore/detail/ipvfoo/ecanpcehffngcegjmadlcijfolapggal">https://chrome.google.com/webstore/detail/ipvfoo/ecanpcehffngcegjmadlcijfolapggal</a></p>
  
  <p>And when I use the CLI to traceroute to the same IP address, it times out??</p>
  
  <p>Are there any diagnostics to figure out or understand why traceroute is timing out in this case?  I thought both traceroute and browsers are using the same OS network layer to route TCP/IP traffic?</p>